re: A use case for TypeScript Generics VIEW POST

TOP OF THREAD FULL DISCUSSION
re: In my case, it was an input element that was bound to the component in Angular. The types were correct, but the form returned strings...

Ah. I'm afraid I don't have enough experience with Angular. I suppose there are other reasons for that miss-type to happen: a library could be exporting the wrong types.

You can see it in the dom, that all form values are strings in the browser. There are no types. When you bin an integer to a form input, it will be a string eventually. When the user modifies it, the new string goes back to the model.

I really wish there were some statically typed version of TS that would be compiled to WebASM... maybe that would be a way to circumvent the JS quirks at runtime.

code of conduct - report abuse