We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The TS allows you to pass arguments with an extended type. As a result, the shape of the object changes but its type does not.
playground
This cannot be fixed at the moment.
https://stackoverflow.com/questions/76490186/use-type-parameters-with-exact-type-instead-of-extending
Therefore, I suggest adding a warning about this.
The text was updated successfully, but these errors were encountered:
If you wanna add @warning JSDocTag description, you can do it with PR.
@warning
Sorry, something went wrong.
You can also add a compile-time check that will generate ts warnings.
You are meaning that generate compiler level warning message whenever calling typia.misc.prune<T>() functions?
typia.misc.prune<T>()
I don't want that.
Not every time, but when necessary, when a generic is passed and it is not equal to the type of the argument.
AlexRMU
Successfully merging a pull request may close this issue.
The TS allows you to pass arguments with an extended type. As a result, the shape of the object changes but its type does not.
playground
This cannot be fixed at the moment.
https://stackoverflow.com/questions/76490186/use-type-parameters-with-exact-type-instead-of-extending
Therefore, I suggest adding a warning about this.
The text was updated successfully, but these errors were encountered: