You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is, these values could actually be null, or undefined (depending on how you ship the data).
TypeScript would not throw an error if you try to use a string method on on any of the string values.
Would it make sense to be able to control how reference types are handled?
The text was updated successfully, but these errors were encountered:
Hey, really cool tool. Tried it on on set of c# code models we have to compare it to our TypeScript models.
This does reveal one issue - some types like
string
could be nullable by default.https://docs.microsoft.com/en-us/dotnet/csharp/nullable-references
An example would be the following conversion:
The problem is, these values could actually be
null
, orundefined
(depending on how you ship the data).TypeScript would not throw an error if you try to use a
string
method on on any of thestring
values.Would it make sense to be able to control how reference types are handled?
The text was updated successfully, but these errors were encountered: