If using Typescript means you want to write less Unit Tests then, actually, I'm all for it. Type away, with JSDoc comments.
But I'm still making you write end-to-end functional browser tests.
Recent searches
Search options
#jsdocs
0 posts0 participants0 posts today
If you think #ai is good at writing #documentation (comments, #JSDocs, commit messages etc.), you misunderstood the whole concept of documentation.
Replied in thread
@thilo I've not used external definitions much personally, except when I need to import a type from a library. @enhance_dev does a great job of using #JSDoc for types in their docs. @see: https://enhance.dev/docs/learn/practices/types
enhance.devEnhance Types - Enhance
@thudfactor Typescript is a good linter, but nobody should ever feel bad about just telling it to ignore and getting back to work. This is why I use #JSDocs instead of #Typescript syntax
Replied in thread
@paulhmason +1 never having a problem with TypeErrors.
But I think types are actually valuable for
A) refactoring (errors can show you all the places your changes have effect)
B) interpreting other people's code (types can provide documentation, not just type)
I avoid using #Typescript syntax though. Linting errors should never prevent you from running code.