-
Notifications
You must be signed in to change notification settings - Fork 0
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
Module schemas need to be added into the schemas_all.yaml file #23
Comments
The workaround for a module document now is just: Was:
Change to:
|
@ronaldtse, clarification request: Maybe you are doing integration testing using the smrl approach? |
@TRThurman Do the resource and module schemas reference each other? If they do, and if they are in the same collection, we need to load both types of schemas in the same instance so the links can be generated. |
@ronaldtse modules reference resource schemas. |
I actually wonder if we should split the resource and module documents into two folders for easier management. |
Maybe, depends how much monkeying around you are doing with the collection files. |
suggestion: keep a stable environment until after the ISO SC4 meeting. |
Right now the collection does not include module documents, so the schemas are not collected inside schemas_all.yaml.
We need to either include all the module documents in the collection, or use a new schemas_all.yaml that includes EVERYTHING.
The text was updated successfully, but these errors were encountered: