Repository navigation
Format web and Python sources, add security and accessibility lint, prepare v0.2.0-beta.4 - #79
Merged
Merged
Conversation
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.
Code hygiene from the post-beta audit, then the version bump for v0.2.0-beta.4. Nothing a person sees on screen changes.
Formatting
pnpm lintnow runsprettier --check. The built bundle has the same CSS and the same screen text. Five web files that end up over the 600-line budget once formatted are frozen at their current size.ruff format --check, and a test keeps both steps in place.Lint rules
article; the dimmed page behind the project drawer is nowrole="presentation"). Six are line exceptions with their reasons.Clean-up
preview-timelineentry point.uiTextalso recognises notices that were saved in Japanese.Release
docs/releases/v0.2.0-beta.4.md.Validation