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
We're trying to move to this package but all our IDs turn into string, losing the additional safety.
My proposed solution would be expanding the existing logic format codegen logic to check for format: typeid and generate the appropriate types.
I will try opening a pull request, but there does not currently seem to be a standardized way for declaring the typeid prefix in OpenAPI (see jetify-com/typeid#45).
The text was updated successfully, but these errors were encountered:
Description
Hi, we are using TypeIDs extensively in our API for IDs. For example
user_...
ororg_...
. Previously we used Typescript like this:To solve ID "confusion" at the type level.
We're trying to move to this package but all our IDs turn into
string
, losing the additional safety.My proposed solution would be expanding the existing logic format codegen logic to check for
format: typeid
and generate the appropriate types.I will try opening a pull request, but there does not currently seem to be a standardized way for declaring the typeid prefix in OpenAPI (see jetify-com/typeid#45).
The text was updated successfully, but these errors were encountered: