Skip to content
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

Update CSS Module contribution doc to include adding new VRT #5205

Merged
merged 3 commits into from
Nov 1, 2024

Conversation

langermank
Copy link
Contributor

Adding some info about adding new VRT tests to the CSS Module contribution doc

Copy link

changeset-bot bot commented Oct 31, 2024

⚠️ No Changeset found

Latest commit: 9d7e375

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@langermank langermank added the skip changeset This change does not need a changelog label Oct 31, 2024
@langermank langermank marked this pull request as ready for review October 31, 2024 19:09
@langermank langermank requested a review from a team as a code owner October 31, 2024 19:09
contributor-docs/migrating-to-css-modules.md Outdated Show resolved Hide resolved
Copy link
Contributor

github-actions bot commented Oct 31, 2024

size-limit report 📦

Path Size
packages/react/dist/browser.esm.js 97.67 KB (0%)
packages/react/dist/browser.umd.js 98.01 KB (0%)

Co-authored-by: Josh Black <joshblack@github.com>
- **Handling `sx` Prop:**
- Confirm the `sx` prop behaves correctly with the feature flag enabled.

#### Visual regression testing

Validate that no visual regressions occur when the feature flag is enabled. The `vrt*` tests are setup to compare the feature flagged component with the original component and will fail if there is a mismatch.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like a good idea! Would we want to make sure we mark them to be removed once the CSS module migration is complete?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we want to keep the dev tests around because they are testing for className override support mainly. When the feature flags are all removed we will then remove the check for enabled vs. default, but we can do that all at once probably since each test uses the same configuration

@langermank langermank added this pull request to the merge queue Nov 1, 2024
Merged via the queue into main with commit d96125d Nov 1, 2024
43 checks passed
@langermank langermank deleted the update-contrib-vrt branch November 1, 2024 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip changeset This change does not need a changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants