I've never said on any channel before, but of course you are the best teacher that dont speak my nativelly language, congratulations you always make everything easily to understand, you have saved me alot of times in my job hahhaha 🎉
Thank you for the great video. Also, can you share the theme and ide settings you used? If you have shared it before and I missed it, please excuse me.
Hey, can you make a full fledged live project on youtube using all the practical libraries like tanstack query, zod, zustand, etc. using Next JS as a framework
Hi Darius, Can you create a video on how to handle error in react without try catch? Because i think it was better to actually handle the error on your own rather than relying on try catch to handle the error for you. Thank you so muuch
thanks for the video, but I still don't understand the meaning of this library when using typescript (if we were talking about js, then yes). But typescript has its own descriptions of models
It's generally used for validation of data that can't easily be typed with TypeScript, as well as to ensure that your types are actually valid during runtime. To expand on that last point, TypeScript transpiles to JavaScript. When you have a TypeScript object that says you should have certain fields/properties, the reality is that you aren't guaranteed to have those fields if they come from third-party APIs or even internal APIs. Validation is just a way to enforce the assumptions made by TypeScript. I find that assuming data is valid when it is not is more dangerous and can create harder-to-spot bugs than going through the effort of verifying that your data is correct at runtime.
I've never said on any channel before, but of course you are the best teacher that dont speak my nativelly language, congratulations you always make everything easily to understand, you have saved me alot of times in my job hahhaha 🎉
Please make a video about axios interceptors and how to manage access & refresh token from backend in reactjs
Yes please.
Yes please
And also the same concept for the react native jwt auth as well please ...
yes please
YES
so valuable. so to the point. i just understood zod for the first time
The way you validated .env file is cool, thanks Darius❤
I never thought zod could be used to validate env variables. Very good approach and very good video.
it is a default in T3 stack
Great video, as always!
I would love to see one with Valibot!
This is what i looking, thanks for explain this topic with easies way ❤ love it
Every tutorial you create is pure gold! Thanks! 🇺🇦
So many useful tidbits in this one. I didn't know about nullish, or the safeParse, or the trick with the environment variables. Thanks, Darius.
I like the bonus part 👍👍👍
Thank you compa, your content is excellent, keep it up.
Nice tutorial and excellent explanation! Can you make a video about Vitest for unit testing? Thank you in advance! Best regards!
once again blast with great content🎉
Thank you for the great video. Also, can you share the theme and ide settings you used? If you have shared it before and I missed it, please excuse me.
Thank you
Perfection
Hey, can you make a full fledged live project on youtube using all the practical libraries like tanstack query, zod, zustand, etc. using Next JS as a framework
Make a video about Tanstack table and router, if possible!
Would be awesome to get a tutorial on how to integrate types generated by Prisma into zod schemas with minimal refactoring each time a model changes.
trpc pls
Hi Darius,
Can you create a video on how to handle error in react without try catch? Because i think it was better to actually handle the error on your own rather than relying on try catch to handle the error for you.
Thank you so muuch
You forget to add date and useFieldArray
the project react is not openeing
thanks for the video, but I still don't understand the meaning of this library when using typescript (if we were talking about js, then yes). But typescript has its own descriptions of models
It's generally used for validation of data that can't easily be typed with TypeScript, as well as to ensure that your types are actually valid during runtime.
To expand on that last point, TypeScript transpiles to JavaScript. When you have a TypeScript object that says you should have certain fields/properties, the reality is that you aren't guaranteed to have those fields if they come from third-party APIs or even internal APIs. Validation is just a way to enforce the assumptions made by TypeScript.
I find that assuming data is valid when it is not is more dangerous and can create harder-to-spot bugs than going through the effort of verifying that your data is correct at runtime.