-
Notifications
You must be signed in to change notification settings - Fork 14
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
Support shared observables instead of enforcing same single listener requirement as underlying googleMap instance #116
Labels
triage me
I really want to be triaged.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
kmayoral
added
triage me
I really want to be triaged.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
labels
Mar 26, 2024
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.@kmayoral Thank you for opening this issue. 🙏
This is an automated message, feel free to ignore. |
Here could be an example implementation (untested):
And an example of how it could be referenced in an existing implementation such as within
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
triage me
I really want to be triaged.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Thank you for this library!
A humble request to this update would be to provide a method to share a single observable instance across multiple callers for every map event type. This could be done by providing a wrapper around the googleMap instance that tracks the inner observable instance state or a static weakreference keyed-by-googlemap-instance type of cache that tracks any previously created observable instances to share out.
In this way, the caller can have multiple streams referencing the same underlying observables without worrying about that streams which were subscribed to earlier no longer receiving emissions.
The text was updated successfully, but these errors were encountered: