-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
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
SUBTABLE field requires type and value.id #448
Comments
@the-red |
Changing these types optional also leads the usage inconvenient because it requires to check whether the type exists or not and disables to infer using discriminated unions. |
@the-red Thank you for your clarification! We'll consider having a solution for this. |
We've merged |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
not stale |
@the-red |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale... 🤮 |
Ref: #447 (comment) |
I generated type definition of SUBTABLE field.
The
type
andvalue.id
properties are required, which makes them difficult to use.I wish the
type
andvalue.id
properties were no longer required.The text was updated successfully, but these errors were encountered: