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

Update spec to require unstable features to be disabled by default #1341

Closed
gregsdennis opened this issue Oct 26, 2022 · 3 comments
Closed

Comments

@gregsdennis
Copy link
Member

Related to #1339, we need to add language that requires implementations to disable unstable features as the default behavior.

@gregsdennis
Copy link
Member Author

In conjuction with #1340, does this mean that a schema with an unstable keyword is expected to error by default?

@jdesrosiers
Copy link
Member

In conjuction with #1340, does this mean that a schema with an unstable keyword is expected to error by default?

Yes. Consumers would need to opt in to using they keywords.

@gregsdennis
Copy link
Member Author

Unstable features are being extracted into the feature life cycle. See #1444

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

No branches or pull requests

2 participants