-
Notifications
You must be signed in to change notification settings - Fork 1
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
Documentation updates #364
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #364 +/- ##
=======================================
Coverage 98.79% 98.79%
=======================================
Files 15 15
Lines 1245 1247 +2
=======================================
+ Hits 1230 1232 +2
Misses 15 15 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 minor queries, otherwise looks great!
@@ -601,10 +601,13 @@ def metadata_template(loc: str | Path | None = None) -> None: | |||
|
|||
template = {} | |||
for name, descr in EXP_JSONSCHEMA["properties"].items(): | |||
if name in EXP_JSONSCHEMA["required"]: | |||
description = f"<REQUIRED {descr['description']}>" | |||
if "const" in descr.keys(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% sure I follow what this addition is doing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the schema defines the name
should be a const
, it dumps that straight into the output YAML, instead of the description.
So, before, if you ran metadata-template
, the first line would be:
schema: <The version of the schema (string)>
If the user leaves that in and doesn't update it to match the current schema version, metadata-validate
will fail.
With this change, the first line of metadata-template
output will be:
schema: 1-0-3
Closes #353 and closes #362 .
This PR adds documentation updates to:
access-nri-intake-catalog
without Gadi access;metadata.yaml
file;A small code edit was also added - the
metadata-template
utility function will now automatically add the correctschema_version
constant to the templatemetadata.yaml
output.