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 @wycats and
especially as the "right thing" will now be preserved after renaming the thing. Unlike when using default. If we all agree what is right,
1 reply 0 retweets 1 like -
Replying to @mweststrate @robpalmer2 and
I don't agree with your characterization of "what is right" which is why I think this is a linting rule rather than language enforced.
1 reply 0 retweets 0 likes -
Replying to @wycats @mweststrate and
If you rename a file and don't rename its main export (easy mistake to make) you have a problem at least as bad if not worse.
2 replies 0 retweets 0 likes
If you rename a file and the imports referring to it use a local name that isn't the same as the file... So what?
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.