-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support converting chrono::NaiveDate to Dart #1833
Labels
awaiting
Waiting for responses, PR, further discussions, upstream release, etc
enhancement
New feature or request
Comments
Sure! Looking forward to reviewing and merging #1834 :) |
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. |
It is still currently worked on trying to keep up with resolving conflicts with origin/master and adapting to CI requirements. |
fzyzcjy
added
the
awaiting
Waiting for responses, PR, further discussions, upstream release, etc
label
Jun 21, 2024
(Mark as |
TrackerSB
changed the title
Support converting chrono::NativeDate to Dart
Support converting chrono::NaiveDate to Dart
Jun 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
awaiting
Waiting for responses, PR, further discussions, upstream release, etc
enhancement
New feature or request
Recent updates of the dependency to allo-isolate introduced support
chrono::NaiveDate
in FRB. However, when converting a Rust struct containing a field of typechrono::NaiveDate
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: