Docs: Write blog post on the history of ban-types, {}, and object/Object #9103
Labels
documentation
Documentation ("docs") that needs adding/updating
team assigned
A member of the typescript-eslint team should work on this.
Comments
|
Yes, I think there's a lot of room for education here in the blog post... |
3 tasks
|
Linking to microsoft/TypeScript#60582 here for visibility |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before You File a Documentation Request Please Confirm You Have Done The Following...
Suggested Changes
One of the particularly exciting changes in our upcoming
v8version is us finally fixing up messaging around the{}(empty object type). It's long been a contentious part of theban-typesrule:{}is a confusing type that a lot of TS devs get tripped up overWe think we've reached a good compromise for v8 with the combination of:
{}, splitting out a dedicatedno-empty-object-typerule: Enhancement: [ban-types] Split the {} ban into a separate, better-phrased rule #8700 -> feat(eslint-plugin): split no-empty-object-type out from ban-types and no-empty-interfaces #8977Number, splitting out a couple of rules: Enhancement: [ban-types] Split into default-less no-restricted-types and more targeted type ban rule(s) #8978 -> feat(eslint-plugin): replace ban-types with no-restricted-types, no-unsafe-function-type, no-wrapper-object-types #9102This has been a long journey with lots of discussion (#8700 is just one of many!). It seems ripe for a blog post to me!
💖
Affected URL(s)
https://typescript-eslint.io/blog/*
Note that if this is accepted, I think a member of our team should write the post. It's not something an external contributor could easily do. Blog posts are tricky.
The text was updated successfully, but these errors were encountered: