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.

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

Section for default values #35

Open
Olivercomputing opened this issue Jun 29, 2018 · 1 comment
Open

Section for default values #35

Olivercomputing opened this issue Jun 29, 2018 · 1 comment
Assignees
Labels
CLARIFY Need for clarification

Comments

@Olivercomputing
Copy link

In a recent discussion with Jim Northey and Don Mendelson, the topic of default values (e.g. for the 'presence' attribute) came up. It was agreed that, rather than having these values be simply by external convention, that they should be explicitly specified once in a new section in the Orchestra file.

The issue of "default defaults", or globally default values which are determined to be most logical by the FPL community, can be handled by providing them in an initial template for new Orchestra files, which should be made available in any case for de novo development.

@donmendelson
Copy link
Member

Use cases would be helpful for defining requirements.

@kleihan kleihan self-assigned this Aug 9, 2024
@kleihan kleihan added CLARIFY Need for clarification and removed enhancement labels Aug 21, 2024
@kleihan kleihan moved this to In progress in Orchestra v1.1 RC2 Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLARIFY Need for clarification
Projects
Status: No status
Development

No branches or pull requests

3 participants