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
Please update the Documentation and point out that Typia only works well with primitive types.
It's frustrating if you use a Validator to prevent runtime errors but just get them on another unexpected Place.
It's known that Typia don't work with classes (creates a Object without the methods).
@ samchon/nestia#431
Current nestia does not performan class conversion, and recommends to use pure interface type instead.
But no Words about it in the Typia Documentation.
And I don't understand why typia.createRandom<Date>() returns to a valid Date class but typia.json.assertParse<Date>(new Date().toISOString()); asserts a string as Date.
The text was updated successfully, but these errors were encountered:
Got it, will write the word that typia is not write the intanceof statement.
samchon
changed the title
Make clear that Typia does not perform class conversion => Typia is not 100% Type-safe
Make clear that Typia does not perform class conversion
Nov 17, 2023
Example
⏯ Playground Link <= first take a look at this
Feature Request
Please update the Documentation and point out that Typia only works well with primitive types.
It's frustrating if you use a Validator to prevent runtime errors but just get them on another unexpected Place.
It's known that Typia don't work with classes (creates a Object without the methods).
@ samchon/nestia#431
But no Words about it in the Typia Documentation.
And I don't understand why
typia.createRandom<Date>()
returns to a valid Date class buttypia.json.assertParse<Date>(new Date().toISOString());
asserts a string as Date.The text was updated successfully, but these errors were encountered: