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
Is your feature request related to a problem? Please describe.
Its not documented and non intuitive that the ui_state attribute can only be used with something that is exactly called RustState
Describe the solution you'd like
Allow for arbitrary struct naming of a struct annotated with ui_state
Describe alternatives you've considered
Warn the user if he uses the ui_state attribute on a struct that is not exactly RustState and document this implicit behavior.
The text was updated successfully, but these errors were encountered:
Totally agree, we should support that! (Originally it was more like a quick demo so was quite minimal) Feel free to PR, alternatively I will work on it later (may not guarantee to be within days since this is related to experimental feature).
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue.
Is your feature request related to a problem? Please describe.
Its not documented and non intuitive that the ui_state attribute can only be used with something that is exactly called
RustState
Describe the solution you'd like
Allow for arbitrary struct naming of a struct annotated with ui_state
Describe alternatives you've considered
Warn the user if he uses the ui_state attribute on a struct that is not exactly
RustState
and document this implicit behavior.The text was updated successfully, but these errors were encountered: