Repository navigation
Conversation
|
Love the idea. In my experience complexity tools miss a lot of context, what do you think about making it non-fatal? Imagine you add one new method to a class and it overflows 20->21 functions, I don't think it should block a release. In most cases, it's a better solution than moving the method to a different scope or some other re-architecture |
How to surface it without making it non-fatal? |
|
Closing: every package that was here has moved to appwrite/appwrite |
Summary
bin/monorepo checkand the root toolchainbin/monorepo complexity <name...> --generate-baselinefor intentional baseline updatesInitial findings
At the limit of 20, the cognitive-complexity baseline contains 49 violations across 18 packages. The largest concentrations are
dns(10),vcs(7), andmessaging(7).Verification
bin/monorepo complexity— passes with 49 existing violations ignoredcomposer validate --strict --no-check-publishphp -l bin/monorepoxmllint --noout phpcs.xmlbin/monorepo validatevale README.md CONTRIBUTING.md CLAUDE.md docs packages— 0 errors (7 existing advisory warnings)git diff --check