Repository navigation
test: checks for the register work - #135
Merged
Merged
Conversation
added 6 commits
November 1, 2026 21:58
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 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.
Adds the checks the register work lands on. Stylelint now fails on an unknown custom property,
scripts/design.test.jspins theme values and watermark contrast,scripts/theme.test.jsrunstheme.jsunder vm, andnpm run check:layoutsweeps every page in the installed Chrome at 320, 375 and 1280, by hand before a deploy. No file underdocs/changes. Each check went red once on a known-bad input, including text overflow underoverflow-x: clip.