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

issues around required projections schema field "configuration" #206

Open
dylanmcreynolds opened this issue Feb 12, 2021 · 1 comment
Open
Assignees

Comments

@dylanmcreynolds
Copy link
Contributor

The schema for projections requires a field called "configuration" be added at the top level of the projection:

"required" : ["projection", "version", "configuration"]
.

This was intended to be a field to be used to help describe and potentially select a projection, but the fact that it required is a bit annoying and confusing to be implementing projections.

Either it should be better described in documentation or made not required.

@danielballan
Copy link
Member

I would support making that optional.

I guess the tension is between "Make the minimal example simple" and "Avoid hiding features people might soon need when they get beyond the minimal example." But I lean toward making it optional in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants