Open
Conversation
Author
|
Fixes #6 |
|
I also like the idea of enabling the package to fetch geo locations once as And actually, the package below, heavily inspired by geoflutterfire/geoflutterfire2, is released a few weeks ago with full respect! https://pub.dev/packages/geoflutterfire_plus https://github.com/KosukeSaigusa/geoflutterfire_plus
If you are interested, please check geoflutterfire_plus! Of course, feature/pull requests are always welcome🙌 Sorry for the comments from outside! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new method, singleWithin, that allows users to retrieve documents near a given point as a single Future, instead of a Stream. This feature is particularly useful for users who only need to access the data once, as it simplifies the process and reduces overhead.