From that statement, it seems to me that they behave the same for assignment.

The index signature `{ [s: string]: any }` in TypeScript behaves specially: it’s a valid assignment target for any object type. This is a special rule, since types with index signatures don’t normally produce this behavior. - devblogs.microsoft.com/typescr

My wife says I’ve gone overboard with stickers. 🤷‍♂️

Thanks to @dotconnor_@twitter.com for implementing this feature 🙌

New in the Refined GitHub browser extension:
It now displays download count for release assets.

// @typescript@twitter.com @drosenwasser@twitter.com

Are there any practical benefits of using the type `{[key: string]: any}` over `object` for function parameters?

Pull request tip: Instead of asking a lot of questions, propose solutions. The more questions I get as a reviewer, the longer it will take for me to review PRs. If you want to increase the time/likelihood of getting your PR merged, make it as easy as possible for me to merge it.

Looking for feedback on a new ESLint rule that adds expiring TODO comments. You can, e.g., define that a TODO expires on a certain date or after a certain dependency is updated. This is meant to help prevent TODO comment rot. (Comment on the PR, not here) github.com/sindresorhus/eslint

Radar: Built-in system apps should not have the "Enter Full Screen" menu item in the "Window" menu
openradar.appspot.com/radar?id

Show more
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!