Skip to content
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

Add mock finder #2832

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add mock finder #2832

wants to merge 2 commits into from

Conversation

lauraghiorghisor-tw
Copy link
Contributor

[mock finder for spike]

@lauraghiorghisor-tw lauraghiorghisor-tw force-pushed the generalize-schema-spike branch 3 times, most recently from 1605832 to 8c0c839 Compare August 7, 2024 16:42
At the moment it is incredibly tedious to maintain the vast amount of document types and their facets for specialist documents. Unsure there is a lot of value in having these strict schema validations when a more relaxed one that doesn't check "valid values" for each field should be enough. This proof of concept works for publishing a specialist document.

NOTE: for the sake of spike, the schemas have been directly manipulated to remove the enum for "document_type". if build schemas is rerun, we will lose this configuration.
NOTE 2: another option is to remove enums entirely for document type across all schemas - this will also save us from having to add it to content_schemas/allowed_document_types.yml and content_schemas/formats/specialist_document.jsonnet . The question will then be whether or not that swings too far the other way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants