Skip to content

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

Conversation

odrakes-cpr
Copy link
Contributor

@odrakes-cpr odrakes-cpr commented Jan 8, 2025

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.

  • Skip auto-tagging
  • Patch
  • Minor version
  • Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.

Notes:

  • If none of these options are selected, auto-tagging will fail
  • Where multiple options are selected, the most senior option ticked will be
    used -- e.g. Major > Minor > Patch
  • If you are selecting the version in the list above using the textbox, make
    sure your selected option is marked [x] with no spaces in between the
    brackets and the x

Osneil Drakes added 2 commits January 8, 2025 15:33
@odrakes-cpr odrakes-cpr requested a review from a team as a code owner January 8, 2025 17:27
Copy link

linear bot commented Jan 8, 2025

@odrakes-cpr
Copy link
Contributor Author

Screenshot 2025-01-08 at 17 25 03

Osneil Drakes added 4 commits January 8, 2025 17:59
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
… param to the search endpoint, so we werent retrieving any families related to the geography
@odrakes-cpr
Copy link
Contributor Author

drive by fix on the geographies filter
before
Screenshot 2025-01-09 at 15 54 12

after

Screenshot 2025-01-09 at 15 56 00

Osneil Drakes added 4 commits January 9, 2025 19:45
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
@odrakes-cpr odrakes-cpr requested a review from katybaulch January 9, 2025 20:11
Copy link

@jamesgorrie jamesgorrie left a 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.

@odrakes-cpr odrakes-cpr merged commit 541880b into main Jan 13, 2025
8 checks passed
@odrakes-cpr odrakes-cpr deleted the feature/app-96-update-admin-frontend-to-support-multigeographies branch January 13, 2025 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants