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
In the current state of things, if a parent class adds a new member, child classes in other libraries would no longer compile until they are re-generated, which is problematic (it turns a non-breaking change in TS into a source-breaking change in go).
This is because we currently don't embed the parent type in the child classes, so they do not "inherit" parent members automatically.
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
🐛 Bug Report
In the current state of things, if a parent class adds a new member, child classes in other libraries would no longer compile until they are re-generated, which is problematic (it turns a non-breaking change in TS into a source-breaking change in go).
This is because we currently don't embed the parent type in the child classes, so they do not "inherit" parent members automatically.
The text was updated successfully, but these errors were encountered: