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

[RFE] Expose optional attribute toggle in schema config #74

Open
afflom opened this issue Aug 26, 2022 · 1 comment · May be fixed by #124
Open

[RFE] Expose optional attribute toggle in schema config #74

afflom opened this issue Aug 26, 2022 · 1 comment · May be fixed by #124
Assignees
Labels
enhancement New feature or request

Comments

@afflom
Copy link

afflom commented Aug 26, 2022

What is the problem you're trying to solve
All attributes within the schema are currently required to be set on all collection items

Describe the solution you'd like
Expose optional attribute toggle in schema config that allows for attributes to be marked as optional.

@afflom afflom added the enhancement New feature or request label Aug 26, 2022
@afflom afflom mentioned this issue Aug 26, 2022
11 tasks
@afflom
Copy link
Author

afflom commented Aug 26, 2022

On the topic of required vs optional: There needs to be two categories of "required":

  1. Required keys; where a specific key is required to be annotated to all objects within a collection (with the exception of the schema link)

  2. Required values, where a value must exist within a collection. A good example of this is index.html. index.html needs to be annotated as the entrypoint to the content of the collection. The requirement here should be that only one object within the collection can be the entrypoint and that entrypoint must exist within the collection.

@jpower432 jpower432 self-assigned this Dec 13, 2022
@jpower432 jpower432 linked a pull request Jan 3, 2023 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants