You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
I don't think i can use your api to replicate the same functionality for the reason that your plugin's .query doesn't return a promise (for a good reason, it could be a continuos query and the callback has to be called every time something happen with different results), but i don't see the reason to use the callback approach for the singleEvent: true option where a Promise i think is the best fit.
What i propose is to create a getValue that returns a promise and deprecate the singleEvent: true option so that the query will became only for continuous results.
but that is the best idea that came to my mind at 1am... :) what do you think?
The text was updated successfully, but these errors were encountered:
Hi Eddy, i'm customising the GeoFire-js plugin to fit with nativescript and your plugin and i got into a problem with their .get which is like this:
I don't think i can use your api to replicate the same functionality for the reason that your plugin's
.query
doesn't return a promise (for a good reason, it could be a continuos query and the callback has to be called every time something happen with different results), but i don't see the reason to use the callback approach for thesingleEvent: true
option where a Promise i think is the best fit.What i propose is to create a getValue that returns a promise and deprecate the
singleEvent: true
option so that the query will became only for continuous results.but that is the best idea that came to my mind at 1am... :) what do you think?
The text was updated successfully, but these errors were encountered: