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

Increase clarity around Optional, Required, and Conditional values #74

Open
eddie-knight opened this issue Feb 13, 2024 · 1 comment
Open
Milestone

Comments

@eddie-knight
Copy link
Contributor

Some users have communicated that it is not intuitive to determine whether a particular value is optional. In some cases, this has resulted in users feeling that they must supply much more than the minimum required values.

For example, a section that is not required is sometimes interpreted as being required if a sub-value within that section is required.

@eddie-knight
Copy link
Contributor Author

A potential solution could be to require all descriptions to contain one of three values at the end: Optional, Required, or Conditional

@eddie-knight eddie-knight added this to the v1.1.0 milestone Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant