Sounds overly fussy given TS only cares about class interfaces rather than class names.
-
-
-
Replying to @wycats @robpalmer2 and
It's about name consistency (even after rename) in large code base / teams, don't call same thing Buffer in one file and Blob in another
1 reply 0 retweets 1 like -
Replying to @mweststrate @wycats and
There is still the flexibility to give other name; use 'as', which makes it very clear to reader that you are doing this
2 replies 0 retweets 1 like -
Replying to @mweststrate @robpalmer2 and
So let me make sure I'm understanding. The consistency you're looking for is "anywhere I see Blob in a file it means the same thing", but...
1 reply 0 retweets 1 like -
Replying to @wycats @mweststrate and
Since you can use `as` you can't know that *unless you look at the import*. So how is that different from seeing `extend` and seeing ...
2 replies 0 retweets 1 like -
Replying to @wycats @robpalmer2 and
The diff is being forced to "do it right by default", rather then being forced to think about + needing lint rules to check you did right
2 replies 0 retweets 1 like -
Replying to @mweststrate @robpalmer2 and
I don't think you're counting all the costs correctly. In a non-default world, the module has to come up with a name.
2 replies 0 retweets 0 likes -
Replying to @wycats @mweststrate and
I also don't think this hazard is what you're implying. I've written huge JS module codebases for years and the first thing I do...
1 reply 0 retweets 0 likes -
Replying to @wycats @mweststrate and
...when I want to know what a name is is to ask vscode to jump to the import. Named or default doesn't make that much difference ...
2 replies 0 retweets 1 like
...you can't keep all of the names in your project in your head and module imports are more like params to a func than global IDs
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.