fix(useConsistentTestIt): fix panic when applying code fix#9942
Conversation
🦋 Changeset detectedLatest commit: df3aaba The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 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 |
Merging this PR will not alter performance
Comparing Footnotes
|
Parser conformance results onjs/262
jsx/babel
markdown/commonmark
symbols/microsoft
ts/babel
ts/microsoft
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
✅ Files skipped from review due to trivial changes (6)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds patch changeset entries and multiple linter fix-path modifications that switch from element-level replacement to token-level replacement for several rules (useConsistentTestIt, noFocusedTests, noSkippedTests). Adds a test case for chained Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
The rule was using the wrong method to replace the token, which caused the panic.
fixes #9918
Test Plan
added debug assertions to the batch mutation API, so snapshot tests will be able to detect it now
tested manually on the repro
Docs