-
-
Notifications
You must be signed in to change notification settings - Fork 2
clinic sites #159
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
base: master
Are you sure you want to change the base?
clinic sites #159
Conversation
@gniezen any guidance on how to check up on these failures? I don't seem to be able to log in to redocly. Have I missed some instructions somewhere? |
ac17368
to
9e787bc
Compare
|
@ewollesen We only have three seats for Redocly at the moment, but it seems they automatically add all repo participants when there's a new PR, so the error was that we're exceeding the seat limit. Let's ignore Redocly errors for now, and I'll work with @tjotala to get it sorted when he's back. |
252debc
to
2548f50
Compare
@lostlevels I had to rebase onto the latest master, which included the redocly changes, so unfortunately it's kinda a lot of little changes. No logical/functional changes were intended. Just a lot of renaming to match and YAML formatting changes. |
Update: re-based on top of the redocly changes. Update: re-based on top of changes to remove ordering facility matching BACK-3634
After discussion with the team, we will: - no longer have a GET endpoint to list clinic sites - sites creation/update/deletion will no longer return a list of sites - site creation/update will return only the affected site BACK-3632
After discussion with the team, we will: - no longer have a GET endpoint to list patient tags - patient tags creation/update/deletion will no longer return a list of tags - patient tags creation/update will return only the affected tag BACK-3632
The requirement for having patient counts in the returned sites was removed, and since the implementation was clunky, removing it for now seems optimal. BACK-3632
BACK-3634
REMINDER the backend change to return a 204 on deletion of a site requires a matching frontend change. Deploying to prod without the matching frontend change will break the frontend!