-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
test(react): update stories to fix failing avt #11620
Conversation
✅ Deploy Preview for carbon-components-react ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for carbon-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@@ -10,7 +10,7 @@ | |||
const path = require('path'); | |||
|
|||
module.exports = { | |||
ruleArchive: 'latest', | |||
ruleArchive: '09June2022', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can't use latest
anymore? is this an update on their end?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dakahn I think when we use latest
we run into an issue where the ruleset may change and PRs start failing all of a sudden, even with no related change 😞
One idea was to specify the archive and then we update to the latest archive as they get released. This way, we can still stay up to date but not have to worry about our AVT job being flaky / failing unexpectedly.
This PR updates
accessibility-checker
and resolves a violation that was showing up in some stories (but not the component itself, that seems to be good)Testing / Reviewing
Make sure AVT ci check passes