TypeScript FINALLY fixed this...
2024 ж. 25 Сәу.
15 030 Рет қаралды
TypeScript 5.5 is coming and it promises to solve a massive developer experience issue thats been with us for a while. We're getting inferred type predicates, control flow narrowing for indexed accessess and regex syntax checking!
Announcement Blog Post: devblogs.microsoft.com/typesc...
-------
🐦 Twitter (X): jollycod.ing/x
🤓 Personal Site: jollycod.ing/me
💻 GitHub: jollycod.ing/git
JollyUI: jollycod.ing/ui
Have you run into one of these issues before? Excited for 5.5?
<a href="#" class="seekto" data-time="77">1:17</a> that accidental asterisk terrified the shit out of me
haha new syntax just dropped
YIELD YIELD
Why is asterix so scarry ?
@@guruware8612 fuckin' pointers!
@@overoad INTERNAL POINTER VARIABLE
Good fixes and a great showcase. Thank you.
That array.filter was so frustrating at the moment. So glad they finally fixed that.
The dumb filter intellisense always annoy me, this is the greatest change in a while.
finally filter works as expected, thanks for the video 👍
Filter type inferences I have been wanting for as long as i have used typescript, especially with JSDoc where you can't directly say Object is Type, I am going to be updating so quickly when this comes out I can't wait
Yeah filter type inference is a gamechanger.
couldn't one just make an extension himself?
It is why I learnt reduce method. Always bothered me that I had to filter array, then map it, and then add type checks again because it forgets which type it should be.
thanks for sharing.
Damn, that's so sick. I always wished for this, but wasn't holding my breath- what a nice surprise.
I'm so happy to know I won't need `.filter((data): data is Exclude => !!data)` anymore!
Holy 🐄 I've been figuring these issues a lot lately
Great explanation mate!
Nice. I hit this problem all the time.
fuck yeah, digestible typescript news, let's go ;-)
For the constant index accesses, it seems very helpful, but will that really be okay? Sure the regular indexing won't cause any side effects, but proxies exist! It'd be severe abuse of notation, but theoretically `proxy[key]` needn't return the same value, or even the same type of value both times, right? Will TypeScript be able to understand this, or will we be able to tell it that explicitly somehow? Or is this just broken with no fix?
what if obj[key] return another object the next time you call it after the check?
I have this filter issue ALL the time
Finally, this feature was way overdue.
So it got a string instead of a "schtring" - great. And more awesome, typescript finally recognizes types !! Then i bailed out.
Hope it doesn't make typescript slower than it already is.
Nice showcase ty! Sidenote: you should really put some effort to learn how to properly touch type, its painful to watch
I actually can, but my current setup uses a wave arm mic which goes right across the centre of my keyboard… Need to get an overhead mic arm!
wow a programmer who doesn’t know blind typing? first time for everything, I guess good content though, even if a bit too lengthy
Someone else mentioned this, it’s more that my mic arm is low profile and goes across the centre of my keyboard so my hands hit it when typing. Need to get an overhead one
Do people actually use TypeScript?...
If you want less headaches from production bugs yeah!
Yes we do
I can't build a production app without typescript these days. When I think of the future. But we have to do a complete rewrite after a few years
If you want to build fast and don't care about types then I guess you just go with js but I originally started with C# and enjoy types so I only use typescript.
is this a joke @nerd
Please this no DX inhancement that what typescript needs to make from version 1 even php have types better than typescript
The Typenscript type system is one of the best existing ones. The limitation here is just JS
@@dave-7117 i think you just making joke here the typescript type system one of the worst i worked with typescript before be the cool thing todo from angular 2 days and i will tell you even php have better type system maybe it does not have all fancy feature and does not support generic but we need to admit that it catches more bugs and does not be on your way please try do thing in laravel, better compiler and error messages and stack-trace for me is better than type-system
@@user-tb4ig7qh9bI think typescript typesystem is pretty nice to work with... wouldn't say it's bad at all
@@user-tb4ig7qh9b stop trolling for attention dude, you’ve gotta be better than this