fix: require fix in suggestion objects
#298
Merged
Conversation
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
1 task
DMartens
approved these changes
Oct 17, 2025
DMartens
left a comment
DMartens
left a comment
There was a problem hiding this comment.
Changes LGTM, thanks for spotting this.
Leaving this open for 2 days if someone else wants to take a look.
github-project-automation
bot
moved this from Second Review Needed
to Complete
in Triage
Merged
9 tasks
lumirlumir
added a commit
that referenced
this pull request
Oct 30, 2025
This reverts commit 02bac50.
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Prerequisites checklist
What is the purpose of this pull request?
This PR updates TypeScript types for suggestion objects so that the
fixproperty is required.This prevents creating suggestions without a fix, which would otherwise cause the runtime error:
It also broadens the type of
datafromRecord<string, string>→Record<string, unknown>because ESLint message interpolation can accept any value that can be stringified.What changes did you make? (Give an overview)
fixrequired inSuggestedEditBase.datatype toRecord<string, unknown>for compatibility with ESLint message interpolation.datato ensure various types are allowed.@ts-expect-errorin test wherefix: nullis used.Related Issues
Is there anything you'd like reviewers to focus on?