-
Notifications
You must be signed in to change notification settings - Fork 178
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
style(app, protocol-designer, components): promote no-unsafe-argument from warn to error, fix all #15402
Conversation
… from warn to error, fix all Promote the typescript eslint rule for no-unsafe-argument to error and fix all outstanding instances in the mono repo
properties: Record<string, unknown> | ||
superProperties?: Record<string, unknown> | ||
} | ||
| { superProperties: { [key: string]: unknown } } | ||
| { superProperties: Record<string, unknown> } |
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.
does this error with the new lint error or is this a random refactor? (asking because i 100% prefer it written this way).
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.
It is a slightly unrelated fix, and probably not necessary here. I'm actually in favor of the index-signature syntax of the Record keyword myself. I think we probably want to relax or invert that typescript eslint rule. I'll tackle that in the next PR.
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.
this is very nice, thank you! 📝 🦖 . i smoke tested PD primarily and bopped around a bit in the app (nevermind i thought i did but it actually whitescreens) but PD looks good to me
Overview
Promote the typescript eslint rule for no-unsafe-argument to error and fix all outstanding instances
in the mono repo
Review requests
Risk assessment
medium, should have no effect on code, but many files were touched