fix(getCheckMessage): add API to return check message #2066
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
WilcoFiers
previously requested changes
Feb 27, 2020
WilcoFiers
approved these changes
Feb 27, 2020
straker
added a commit
that referenced
this pull request
Mar 6, 2020
* feat(getCheckMessage): add API to return check message * throw when invalid
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.
Technically this is a
feat, but we had a breaking change for 3.5.1 that broke eslint-plugin-jsx-a11y, so we need to release this as a patch release so we don't go to 3.6.0.With this, they can use a public API rather than accessing a private interface:
Closes issue: #2060
Reviewer checks
Required fields, to be filled out by PR reviewer(s)