-
Notifications
You must be signed in to change notification settings - Fork 8
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
Passing values to Queries #9
Comments
This sounds like its in the same vein of request as #7. Right now, the queries are a bit static as you've discovered. I'd be happy to have the lib support this feature and would be glad to review a pull request, but I'm not sure when I'll have time to get to implementing this... The tricky thing with queries is that they must be used in the correct combination. The UI does some things to protect a user, but once you allow them to become programmatic, the error handling/throwing will probably need to become a bit more elegant. |
If you take a look at the changes in firebase_on.js in 0c70a7e, I think that should serve as a good starting framework to add this feature. |
I have added the feature where you can pass values to queries from msg , flow or global values see 9bf89aa |
There doesn't appear to be a way to define what I would want query fields to be based on a msg parameter. For example I have a function that defines "msg.fooBar = '[email protected]' ". When I specify my startAt I want to be able to set that value to msg.fooBar. Currently I have to set it to '[email protected]' and that just seems the wrong way to go about doing this.
The text was updated successfully, but these errors were encountered: