fix(getStandards): Read standards from utils #2903
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
straker
previously requested changes
Apr 29, 2021
|
@stephenmathieson I'm adding this so we can use the standards objects outside of axe-core. Makes it a little easier to use them in custom evaluate functions and the like. |
Co-authored-by: Steven Lambert <[email protected]>
straker
approved these changes
Apr 30, 2021
|
Should this be considered a feature commit since it's adding something to the public API? |
|
@stephenmathieson If it was added to |
straker
added a commit
that referenced
this pull request
May 18, 2021
* fix(getStandards): Read standards from utils * Update lib/core/utils/get-standards.js Co-authored-by: Steven Lambert <[email protected]> Co-authored-by: Steven Lambert <[email protected]>
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.
Should have made this info available before. Not sure why we overlooked that.
Closes issue #2889