You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Low Risk
Low risk documentation-only change; no runtime code or APIs are modified.
Overview
Adds a new TypeScript guideline section explaining when callback parameter types must use any under --strictFunctionTypes due to bidirectional assignment constraints.
Includes a concrete Wide/Narrow example comparing unknown, never, and any, plus a note and real-world references clarifying that this any usage is intentionally scoped to the parameter position and not meant to be broadly propagated.
Reviewed by Cursor Bugbot for commit 5f5cc8f35abcf4dd8fca7c959ae6aee7b21d777d. Bugbot is set up for automated code reviews on this repo. Configure here.
View rendered version
Note
Low Risk
Low risk documentation-only change; no runtime code or APIs are modified.
Overview
Adds a new TypeScript guideline section explaining when callback parameter types must use
anyunder--strictFunctionTypesdue to bidirectional assignment constraints.Includes a concrete
Wide/Narrowexample comparingunknown,never, andany, plus a note and real-world references clarifying that thisanyusage is intentionally scoped to the parameter position and not meant to be broadly propagated.Reviewed by Cursor Bugbot for commit 5f5cc8f35abcf4dd8fca7c959ae6aee7b21d777d. Bugbot is set up for automated code reviews on this repo. Configure here.
Originally posted by @MajorLift in MetaMask/contributor-docs#170
Originally posted by @lannathompson65-arch in https://github.com/MoneyDailyTipsPro/moneydailytipspro/issues/1