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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add nullable annotation for boolean field #23
Conversation
@kevmoo I've fixed the particular case. I can do it for other field types or if you show me another way I can do it as you show me. |
@zolotyh – I tweaked some things here. You'll want to sync down master locally. Please add a test here – at least modify one of the existing examples in the test directory to use this feature. |
@kevmoo Thank you for your answer. I've done it. If you have any additional requirements just let me know |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was tempted to say we should add some special nullDefault
sentinel or something. But this is cleaner.
Thanks!
@kevmoo Thank you for approving a request. Do you plan to publish a new version to pub? |
Working on that now!
…On Tue, Nov 27, 2018 at 4:03 AM zolotyh ***@***.***> wrote:
@kevmoo <https://github.com/kevmoo> Thank you for approving a request. Do
you plan to publish a new version to pub?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABCirIUWj1OhGMuQBIf3xqY8SfkWb99ks5uzSoqgaJpZM4Yq_Z8>
.
|
Now, build_cli can't generate code which matched this:
dart file.dart // null
I am trying to fix this.