-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/app 96 update admin frontend to support multigeographies #146
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
Merged
odrakes-cpr
merged 11 commits into
main
from
feature/app-96-update-admin-frontend-to-support-multigeographies
Jan 13, 2025
Merged
Feature/app 96 update admin frontend to support multigeographies #146
odrakes-cpr
merged 11 commits into
main
from
feature/app-96-update-admin-frontend-to-support-multigeographies
Jan 13, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- also only display the multi geo selector for mcf corpora
We want to have multi geographies for non legacy corporas - so i have added a variable which checks what the corpora is and renders the geographies multi selector and updates the payload accordinly
…ort-multigeographies
katybaulch
reviewed
Jan 9, 2025
… param to the search endpoint, so we werent retrieving any families related to the geography
…ayload - to prevent things breaking
mcf documents also do not expect anything in the metadata, therefore adding in these values cause a 400
Even when role is marked as notRequired(), its nested fields (label and value) are still validated if the role object exists in the input.
The previous typing didnt really fit into what we were doing, so i have made it a bit more simpler to reflect what we are doing in the yup validation schema. it was just becoming too unecessarily complex, which added to the already complex yup validation was just hell
jamesgorrie
reviewed
Jan 13, 2025
jamesgorrie
approved these changes
Jan 13, 2025
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.
Nice! Couple of code related questions but nothing blocking.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed
Update the form to edit and create families with multiple geographies
Drivebys -
Fix incorrect geography param being passed to the search endpoint
Fix validation error on the document form suppressed
Proposed version
Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.
Visit the Semver website to understand the
difference between
MAJOR
,MINOR
, andPATCH
versions.Notes:
used -- e.g. Major > Minor > Patch
sure your selected option is marked
[x]
with no spaces in between thebrackets and the
x