We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are multiple tests that wrap the rendered component with ThemeProvider: https://github.com/search?q=repo%3Aprimer%2Freact+%3CThemeProvider+path%3Atest.tsx&type=code
We do not have to do this anymore because we already wrap all stories in a ThemeProvider in preview.js.
Note: There might be a couple exceptions so make sure to test this by switching themes in storybook
The text was updated successfully, but these errors were encountered:
👋 What is the impact of the redundant ThemeProvider in tests? Is this a "nice-to-have" quality of life improvement?
Sorry, something went wrong.
Remove redundant ThemeProvider from tests
ea9df69
Fixes #4514 --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/primer/react/issues/4514?shareId=XXXX-XXXX-XXXX-XXXX).
Is this a "nice-to-have" quality of life improvement?
Yep, I'd say this is nice to have. I don't think there are any bugs that are missed because of this redundancy
Successfully merging a pull request may close this issue.
There are multiple tests that wrap the rendered component with ThemeProvider: https://github.com/search?q=repo%3Aprimer%2Freact+%3CThemeProvider+path%3Atest.tsx&type=code
We do not have to do this anymore because we already wrap all stories in a ThemeProvider in preview.js.
Note: There might be a couple exceptions so make sure to test this by switching themes in storybook
The text was updated successfully, but these errors were encountered: