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.

Sign up for GitHub

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

Jump to bottom

Inconsistent use of description and definition in codes #180

Open
luciecastella opened this issue Sep 8, 2022 · 2 comments
Open

Inconsistent use of description and definition in codes #180

luciecastella opened this issue Sep 8, 2022 · 2 comments

Comments

@luciecastella
Copy link
Collaborator

Some projects use description and others definition as code attribute. This should maybe be unified. Which one is more relevant? Maybe description?
@luciecastella
Copy link
Collaborator Author

@danielhuppmann @phackstock

@danielhuppmann
Copy link
Member

Yes, I would move to "description" as the default in new projects, this is also in line with the documentation here.

However, some (legacy) projects have neither of the two, so we should not make it a required attribute (yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danielhuppmann @luciecastella