Repository navigation
Null safety support - #8
Conversation
Remove late from geo Serie type.
|
@synw Could you please check this out? |
|
@duzenko Since synw is not very active on GitHub, could you please look at this pull request, and eventually deploy it on pub.dev? Since there are 11 packages that depends on this one, they are having an hard time migrating to null-safety. |
I don't have write access |
|
By the time the pull request get approved, For Geo Json: For Geo point |
|
Sorry for not being around these days. I should manage to take the time to merge these pull requests and publish to unlock the situation for you guys. Not doing Dart code since a while I am not confident about the null safety migrations, so I have a question: what version number should be the migrated version? Must we use something like 0.9.0-nullsafety.0 or directly upgrade to 1.0.0 or something? What is idiomatic? |
|
Hi
Its fine to release with any version code.
Thanks
On Fri, 25 Jun 2021 at 7:15 pm, synw ***@***.***> wrote:
Sorry for not being around these days. I should manage to take the time to
merge these pull requests and publish to unlock the situation for you guys.
Not doing Dart code since a while I am not confident about the null safety
migrations, so I have a question: what version number should be the
migrated version? Must we use something like 0.9.0-nullsafety.0 or directly
upgrade to 1.0.0 or something? What is idiomatic?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNI3RJPTIZBUR3B7RTAR3DTURFZ5ANCNFSM453TWD4Q>
.
--
-------------------------------------
Thanks & Regards,
Shyam Parmar
+61 470298670
*Linkedin <https://www.linkedin.com/in/shyamparmar/>* | Blog
<https://learning-alight.blogspot.com>
|
|
@synw I don't manage dart packages myself, but from what I can see from different packages published, versions with Since the latest version available today is 0.8.0 and pub.dev follows the semantic versioning, your package is at this time in an initial development phase, so I think 0.9.0 is the right version. However since the number of issues on this repo is basically 0 (except for this merge), and many projects are depending on it, I think it's also safe to release the next version as 1.0.0, to make it clear that it is stable, and in the future the changes would remain backward compatible, unless new features like null-safety are added, which it will require to increase to a new major version. I hope my explanation will help you to decide on what version to apply |
|
Since Repo does not have
If you are running the older version of flutter please upgrade by |
|
You are right my install was completely outdated. Version 1.0.0 is published. Thanks for your work |
No description provided.