Fix Berkeley schema element usage in frontend code #1375
Merged
Conversation
This file contains 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
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.
Just two quick fixes for places where the frontend code was tripping over some Berkeley schema changes:
web/src/components/FacetedSearch.vue: Thegold_path_fieldslot does not have the referenced annotation in the Berkeley schema. The change to add the annotation was merged intonmdc-schemaon July 17 and the last timeberkeley-schema-fy24was synced withnmdc-schemait included changes through July 16. So the annotation should come back eventually. In the meantime this prevents a render-time error.web/src/views/SubmissionPortal/Components/SubmissionContextForm.vue: We just needed to refer to the enum's new name.