This repository was archived by the owner on Oct 11, 2026. It is now read-only.
Repository navigation
test: scope tailwind class scanning - #17
Merged
Merged
Conversation
KyleJune
marked this pull request as ready for review
October 2, 2026 04:48
|
🎉 This PR is included in version 0.4.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
The Tailwind 4 build test scans the package directory by default. Adding the release-note word
isolatechanges its generated CSS and breaks the fixture comparison. Scope class discovery to the fixture directory and capture its complete CSS with the existing snapshot mechanism.Production plugin code and example files are unchanged. Output errors, warnings, path and count still have explicit assertions.
Verification
deno task checkpassed;deno task test --parallel --reporter=dotpassed 7 tests/30 steps, zero failures (2s), inside the parent checkout.Risk
Door: two-way test change. The snapshot checks the entire fixture-generated CSS and normal test runs do not rewrite it. No production behavior changes.
Closes
Nothing. Refs udibo/udibo#1676; the parent dependency PR records integration separately.