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
Recent updates of the dependency to allo-isolate introduced support chrono::NativeDate in FRB. However, when converting a Rust struct containing a field of type chrono::NativeDate a (working 馃憤馃徎) Dart class which extends from RustOpaque is generated.
Despite the fact that this should be enough to technically utilize the Dart class it would be much nicer if it generated a field of type DateTime instead of depending on RustOpaque. This enables quite more capabilities on the Dart side. In my case especially reflection.
The text was updated successfully, but these errors were encountered:
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.
Recent updates of the dependency to allo-isolate introduced support
chrono::NativeDate
in FRB. However, when converting a Rust struct containing a field of typechrono::NativeDate
a (working 馃憤馃徎) Dart class which extends fromRustOpaque
is generated.Despite the fact that this should be enough to technically utilize the Dart class it would be much nicer if it generated a field of type
DateTime
instead of depending onRustOpaque
. This enables quite more capabilities on the Dart side. In my case especially reflection.The text was updated successfully, but these errors were encountered: