-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/parse bundle and add errors to modal #77
Conversation
….com:gosh-dre/gmsa_genomic_fhir_webapp into feature/parse-bundle-and-add-errors-to-modal consolidating merge updates
Things for feedback:
is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry, missed this for a while. I live by being added to reviews by github so it emails me for reviews but you didn't know that!
error modal should pass, redirect after submission may say conflict
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice to see this working, some outstanding comments from last time still need to be addressed, but basically all stylistic
await waitFor(() => { | ||
expect(screen.getByText(/error/i, { selector: "h2" })).toBeInTheDocument(); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we still need this, worth checking to see if tests pass without it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can go back to the previous way of doing it, that works
closes #74