Migrate to null safety

[AyushBherwani1998]

One of our side project uses this library, would be happy to help to migrate to null safety @johnpryan

[AyushBherwani1998]

There are few blockers

flutter_image is deprecated and no longer maintained under Flutter org.
latlong is archived and is no longer maintained.
positioned_tap_detector has been discontinued
proj4dart is not yet migrated to sound null safety.

[andreystavitsky]

For latlong here is active pull request
#750

[aytunch]

in order for migrating to Flutter 2.0 we will need this library to be null safe. This is a one of a kind package which lets Flutter community to use their beloved widgets as markers. @johnpryan do you have any strategy for this? @AyushBherwani1998 thanks for listing the deprecated dependencies. It might be a good starting point before nnbd migration. I think flutter_image and latlong are not going to be hard to replace. I don't know what proj4dart is for and if there is a replacement for positioned_tap_detector.

[kevin-lot]

For "latlong".
What about "latlng" package ? (that is already null safety compatible)

nb: I didn't check the code https://github.com/xclud/flutter_latlng.

[JAICHANGPARK]

Error: Cannot run with sound null safety, because the following dependencies
don't support null safety:

 - package:flutter_map
 - package:latlong
 - package:logging
 - package:validate
 - package:proj4dart
 - package:tuple
 - package:positioned_tap_detector
 - package:flutter_image
 - package:quiver
 - package:mgrs_dart
 - package:wkt_parser
 - package:unicode
 - package:lists

[jpeiffer]

It looks like latlong was abandoned but someone has forked that and added Null Safety:
https://pub.dev/packages/latlong2

[attex]

logging has been updated to null-safety
tuple has a prerelease for null-safety
quiver has been updated to null-safety
unicode has been updated to null-safety

[aliraghebi]

I think this repo is archived and I'm gonna fork and publish NS version of flutter_map.

[aytunch]

@arsamme thanks. But I do hope it is not the case for flutter_map. I see the owner @johnpryan active from time to time. I would love to hear his opinion about the future of this great package

[aliraghebi]

@aytunch I hope too. But he didn't respond to any issue for a long time.

[proton1k]

@arsamme @aytunch there's a call for maintainers on the top of the issues list on this repo. I assume someone else has to join as an active maintainer so that the package get's timel yupdates. Is there another package available out there or downgrading to pre-null-safety version is one of the ways you manage the production-ready apps ?

[aytunch]

@o1dnik I have missed the call for maintainers issue, thanks for pointing it out. I have been using this library from the very early days. And lately @maRci002 and @lpongetti have done very useful and successful contributions among other developers. As now understanding that @johnpryan is busy with other stuff, I would like to know from you two friends if you have an agenda on this libraries null safety upgrade, maintenance and new features? Thanks.

Lastly, I would like to remind to the developers and marketers of several Map provider companies which are supported by this package that if this package is not maintained anymore, we would most likely change to another provider which offer similar functionality using their official packages. So it would be great to get some help from your side too:)

[aliraghebi]

@aytunch I've submitted call for maintainers form and no answers yet (after about two weeks)