feat(v2): add validation escape hatch #3134
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for docusaurus-2 failed. Built with commit fdd1659 https://app.netlify.com/sites/docusaurus-2/deploys/5f1f00d36d2c550007c4d1b0 |
|
Deploy preview for docusaurus-2 ready! Built with commit cf51d51 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Validation is a new feature, and it's easy to write wrong validation schemas, as we've seen in the recent release (#3120)
This introduces a secret escape hatch that we could give to users if the new validation system gives false positives and rejects a config that used to work.
It's not worth documenting this escape hatch for now because we don't want users to use it without reporting the bad validation logic in the first place.
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
manual