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.
[squad] Implement #53519: Add docs integration, test coverage, and regression checks #53750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[squad] Implement #53519: Add docs integration, test coverage, and regression checks #53750
Changes from all commits
1a5b7e4File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] Importing
validation.tswith a.tsextension relies on Node 22's--experimental-strip-types, which is absent from the existing test infrastructure and undocumented in the Makefile target.💡 Suggestion
The existing
inlineMarkdownInHtml.test.jsimports only.jsfiles. The new test imports a.tsfile directly, which works on Node 22+ (strip-types is on by default) but will silently fail on older Node versions with a cryptic module-not-found error.Add a minimum Node version guard in the Makefile target:
Alternatively, document the Node >=22 requirement in the target comment so future CI upgrades know why.
@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
L55-79: stdlib: hand-rolled
assertThrows/assertDoesNotThrowreimplementassert.throws/assert.doesNotThrowfrom Node's built-inassertmodule. Userequire('node:assert')(strict variant) instead.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] Test label says
'goal category missing text.label is rejected'but the mutation deletes the entiretextobject — a broader failure than the label implies.💡 Suggestion
Rename the label to match the actual mutation, or tighten the test to delete only
text.labelto precisely exercise thehasTexthelper'stypeof value.label === 'string'branch:@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/codebase-design]
type WizardDataModelis imported on line 3 but never used locally — it is re-exported via the separateexport type { ... } from './validation'block on lines 4–10.💡 Suggestion
Remove the redundant named import to keep the module header minimal:
All types flow to consumers exclusively through the re-export block below.
@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The test advances past step 2 without asserting which trigger option is selected, making the destination-inference assertion fragile.
💡 Suggestion
The destination "Post a comment" is inferred from the selected trigger type. If the wizard's default trigger changes, this test will silently start testing the wrong path. Explicitly select a trigger before clicking Next so the test reads as a specification:
This makes the intent clear and decouples the assertion from whatever the wizard happens to pre-select.
@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.