Repository navigation
docs(signals): add missing diagnostic guide sections - #3785
Conversation
🦋 Changeset detectedLatest commit: 1c11048 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…rces; two wording fixes
HUGE_FAN_IN is the always-on backstop at 2000 tracked sources and emits only the
computation's name and `data: { count }`; the source list belongs to
WIDE_SCOPE_DEPS (attribution engine, threshold 30, up to 12 names). Also joins a
stray hard wrap in ASYNC_OUTSIDE_LOADING_BOUNDARY and, since
SETTLE_WALK_UNINITIALIZED_SOURCE is severity error, says "silencing the
diagnostic" rather than "hiding the warning". Every heading is kept.
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
|
Coverage Report for CI Build 37285535127Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage remained the same at 75.991%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Eight diagnostic guide URLs point to missing sections. Four codes share combined headings, and four newer codes have no section yet.
Add individual sections for all eight codes, preserving the existing combined headings so their links continue to work. Add a test that reads
DiagnosticCodeand checks that everyDEV.guideUrlfragment has a matching section in the guide. It currently covers 65 codes.Validation: the test failed for the missing sections before the documentation changes; all 32 tests in the selected diagnostics files now pass. Prettier and
git diff --checkpass.