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
If you export an enum from Rust it's possible to provide values for multiple variants on the frontend due to the fact that | is typescript is not exclusive or.
I don't think this is a problem with adjacently tagged enums.
If you export an enum from Rust it's possible to provide values for multiple variants on the frontend due to the fact that
|
is typescript is not exclusive or.I don't think this is a problem with adjacently tagged enums.
This article is a good rundown: https://effectivetypescript.com/2021/11/11/optional-never/
Eg. this demo needs to not compile:
I think we would have Specta generate
{ a: string; b: never; } | { a: never; b: string; }
instead which would cause the appropriate errors.For personal reference this came up with
search.paths
in SD.The text was updated successfully, but these errors were encountered: