-
Notifications
You must be signed in to change notification settings - Fork 0
refactor: ♻️ rename check() arg from descriptor to properties
#143
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
refactor: ♻️ rename check() arg from descriptor to properties
#143
Conversation
| @@ -1,36 +1,43 @@ | |||
| --- | |||
| title: "Checking a Data Package descriptor" | |||
| title: "Checking a Data Package's properties" | |||
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.
We could also use "metadata" here, as I've done on the landing page now #141
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've started to wonder if we can stop using the word "descriptor" entirely, using either metadata or datapackage.json instead (whichever is appropriate in the context) when talking about the JSON file and then properties otherwise. What do you think?
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 ok with that 👍 simpler, clearer, plainer language is something I always appreciate!! 😁
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.
👍 looks good to me 😁
Description
Again following that we've agreed to use the word "properties" about the descriptor's content loaded as a
dict.Related to #104
Needs an in-depth review.
Checklist
just run-all