-
Notifications
You must be signed in to change notification settings - Fork 144
How to query for nested objects 2 levels down? #150
Comments
I also seem to be getting a |
I think you stringify the whole body, not just the query parameter. As for the ES syntax, it looks like you're trying to use deeply nested data structures. Those aren't going to work well with Flashlight or ES. You also shouldn't use arrays with distributed data. But I can't be any more specific without some context on what the data structure is you're trying to index and what your config.js paths look like. |
Config paths:
So my database looks like this (visually presented):
I kinda don't want guestlist to be its own list with a reference to an event because that will complicate things. Surely I must be able to just go into an event and search the guestlist from there? As for the stringifying, I'm doing this: |
Look at the code I linked you to. You don't stringify components of As for the nested query portion, that's purely ES. Looks like this article might help to understand how it should work. |
When I stringify the entire body I just get permission denied errors because of the security rules that you provided, do I have to do anything else? |
Hi I think I am having the same issue, except I am able to stringify the body and post the request to my Firebase instance. What happens next is that Flashlight never writes the response back. |
OK looks like #136 fixed the issue for me! |
This can't be right (why I think this is wrong is because I get an error as well as this query being ridiculous to write):
For data that looks like this:
The error I get is
Which is also mentioned in #144. Some help with this would be appreciated since I find the docs for nested queries on both ES site and here a bit vague.
EDIT: So after stringifying the query of
body
it doesn't throw me error anymore, but I'm still not getting any results despite searching for exactlyChris Woodland
. So I'm guessing that my query structure is off somewhere.The text was updated successfully, but these errors were encountered: