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
Describe the bug
While is was working with this library I stumbled in to, as far as I could tell, breaking behavior. I had a setup similar to the following:
Notice that after key, the colon should be the in keyword. Is there away for ts-rs to be aware of this in the future? For know I just have a post processing step that makes that change, but it seems like this behavior is not intentional.
Describe the bug
While is was working with this library I stumbled in to, as far as I could tell, breaking behavior. I had a setup similar to the following:
When I translate
ComponentId
I get the expected output:However when generating the ts file for
Entity
I get the following:This throws an error as it is not the correct format. Since
ComponentId
is a literal type, the correct translation should be the following:Notice that after
key
, the colon should be thein
keyword. Is there away forts-rs
to be aware of this in the future? For know I just have a post processing step that makes that change, but it seems like this behavior is not intentional.To Reproduce
Steps to reproduce the behavior:
enum Component { foo, bar}
,struct Entity { components : HashMap<ComponentId, Component> }
TS
for all types madeExpected behavior
When generating the types listed above,
Entity
should generate the following:Version
The text was updated successfully, but these errors were encountered: