This is why learning typescript generics is important
Вставка
- Опубліковано 16 вер 2023
- 📘 T3 Stack Tutorial: 1017897100294.gumroad.com/l/j...
🤖 SaaS I'm Building: www.icongeneratorai.com/
✂️ Background Cutter: www.backgroundcutter.com/
💬 Discord: / discord
🔔 Newsletter: newsletter.webdevcody.com/
📁 GitHub: github.com/webdevcody
📺 Twitch: / webdevcody
🤖 Website: webdevcody.com
🐦 Twitter: / webdevcody
You're like if "Common Sense" was a programmer. You don't have any ridiculous esoteric pseudo-advice to give, but you just stick to the basics and make cool stuff. Validates "the basics" in a climate where you either use vim and program in c/rust, or you use vscode and write next 13 apps. I'm really glad I found this channel.
The more difficult parts of TS (generics, mapped/recursive/conditional types, etc) are not easy to learn from the docs by themselves. Gabriel Vergnaud's Type-Level TypeScript was a really helpful resource for me, and I've heard good things about TypeHero
"That's something that's really important when building a libary, is start with the interface - how a people paying to consume your functions / interface"
Such a valuable tip, applies to any function / structure; it helps a lot to find a good "how" to think about the user first.
Really good content! Not much new stuff in this video for me, but subbed for the conciseness and the calming voice.
Great quality of info, nicely done 👍
Such an amazing tutorial. I used it before to create a local storage hook, which is one of those rare cases where you have to create a generic function.
I used it for the same situation a few days ago. good stuff
Such an amazing educative content. I learned a lot from you. And I am applying it to my and my company's codebase.
To the point. As per usual, Cody delivers! Keep it up!
This video was fantastic, thank you so much Cody. I was at the stage of having a firm grasp of 'theoretical' Typescript but this ~14 minute video has really made the penny drop for me. You have a real talent for pedagogy, don't ever stop!
It’s a great video, thank you. I hope there will be more videos about this topic. Great work!
Such a great video! This made me realize that not all TS is difficult and actually fun to write. Love the content, keep it up!
Well done explaining generics! You earned a new subscriber
Didn't take you long to become my favourite tech UA-camr. Perfect no-nonsense approach to videos, ability to call things out for what they are and diving into technical content like this and that custom framework you're on currently. Your videos are a goldmine when it comes to reaffirm knowledge and see different use cases for different strategies.
Really appreciate the work you're putting into this channel and its content!
Thanks man!
Fantastic video, great job 👏
This was extremely helpful.
great videos man , i eat breakfast while watching your videos , always great content , keep it up man !!!
This was impressive, generics seems to be my next step in understanding TS. :D
Thanks for the video!
Im not a guy of typescript but I try to learn on the future. This video was awesome about generics good example and explain.
Great video, to the point!
Nice tuts 👍
super cool, i build something similar a month ago because i just wanted redux toolkit kind of functionality in an old angular js file using rxjs
i had to use jsdocs but still works nice
Dont stop making videos ever lol some of these random topics end up saving me in my project
Wow! Thanks!
Good job babe!!
Thanks Cody
Awesome video!
6:11 extends key of TStore
7:19 using generic to control user set input
9:12 callback signature
12:14 ReturnType
Though there is not "class keyword" involved, but the way you handle it is just OOP, because you want all the "object" to inherit the get/set function, that's why the "generic" kicks in. It could be a pattern for library author, but pretty much not for application level app.
nice one!
I just used it while creating a hook for storing my items in local storage
I tried using this pattern with useMap hook in react, The definition is the same for this and useMap, but the useMap value type has type of all values combined.
As I was watching I was wondering the difference between and . I guess I'm more familiar with the second structure.
❤
this is good, and thanks for the video.
This question is off-topic, but I wanted to ask if the glasses you are using are some kind of blue filter glasses. I've been having dry eye-related issues lately because of coding.
Thanks for all the videos.They are very valuable.
No they are just normal glasses
I too had the same problem when working on my side project. Nextjs caching is too aggressive imo. For invalidating router cache, they provide the router.refresh().
As a senior JavaScript/TypeScript developer, if you're considering branching out into another backend programming language, what would be a wise choice? Many developers commence their journey with JavaScript, and the job market is becoming increasingly competitive in this domain. In this context, how do you view languages like Go, Ruby, and Java?
I’d be interested in working with go personally
this is solid lol
Can you do a video showing us your VSCode theme?
it’s bearded stained blue
The video reminds me on the days where u used to hate TS 😅
Anyway
Very cool video 🎉
I’m less of a noob now 😆
Is this a shades of purple theme?
Bearded theme stained blue
@@WebDevCody thanks ser!
Just asking but why not just make a class for the store and use a constructor? Trying to learn TS.
No reason, I just default to functions usually
Class based programming is a style, and so is functional programming. You can pick whatever you want. All companies I worked for though, their projects are functional. Classes are annoying to work with, or rather OOP style.
Do get/set really require generics here? Since types for those are constructed from passed in data there is no need to be able to pass generics to those functions to tell it what types it has or to override/extend something. Instead of using K for example, I think for this particular case it would be better to just write "key: keyof T" without exposing generics here.
Good example nonetheless!
doing this way, you lose type inference for the values
by making a generic constraint, typescript will infer the value at the specific key declared as K
T[keyof T] is the union of all types of T attributes
@@VictorMachadoDeFranca You are right. I had to see it for myself and I tested this and by not using generics in this example and using what I said in my comment, return type for .get() will be a union of all types from all keys of T. Same goes for .set(), value accepted will be a union of all those types. Huh, I thought generics were unnecessary here, but I guess I was wrong.
Well, you learn something new every day :D
I guess typescript isn’t smart enough to know what key specifically is being passed into the callback
Is this future me?
I really hope not, because I don't like javascript that much
0:20 as a non ts dev, I almost vomit seeing that code just for "dev-friendly-development"
As a TS dev, I almost vomit seeing your stupid comment.
Why? At 20 seconds in the only typescript code I use is defining a type and passing a generic
Yeah, you have never use generics in any language :)
2 space indention is hard for my eyes
sorry, it's the format I use
it's very cool but nobody should call that "easy to read".
Generics seem kinda complex and off-putting to me.