-
Notifications
You must be signed in to change notification settings - Fork 2
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
Implementation of schema build functionality that enable the maintenance of schema modules instead of a single large schema specification #143
Labels
enhancement
New feature or request
Comments
jh-RLI
added a commit
that referenced
this issue
Jun 5, 2024
jh-RLI
added a commit
that referenced
this issue
Jun 5, 2024
…l of the schema: describe the oemetadata collection/resources (includes 1:n resources) #143
jh-RLI
added a commit
that referenced
this issue
Jun 5, 2024
…o version specific source_build directory #143
jh-RLI
added a commit
that referenced
this issue
Jun 5, 2024
jh-RLI
added a commit
that referenced
this issue
Jun 5, 2024
The implementation is now complete with #180 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the issue
The schema.json that is part of each oemetadata release becomes more and more complex. It would be better to introduce modules that only hold parts of the schema content. Therefore we need a process that can resolve & merge the modules into its complete state by assembling the parts.
Ideas of solution
Workflow checklist
The text was updated successfully, but these errors were encountered: