Repository navigation
Size and complexity lint growth warns during feature work (h3-studio#899) - #362
Merged
Merged
Conversation
…899) Owner 2026-10-31: build features without fighting size limits, refactor afterwards. check:lint now prints complexity and max-lines-per-function growth as warnings; every other ratcheted rule still fails.
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.
Owner 2026-10-31: feature work should not be shaped by size limits; refactor afterwards (h3-studio#899).
tools/check-lint.mjs: growth incomplexityandmax-lines-per-functionprintswarn (refactor later) …and passes. Every other ratcheted rule (unused vars, hook deps, parse errors…) still fails. The baseline is unchanged, so the warnings list exactly what the refactor pass has to bring back down.