-
Notifications
You must be signed in to change notification settings - Fork 140
add handling of objects to processQuery #57
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
Conversation
1 similar comment
Please change the target branch from |
How can I run the query ( {
"one":{
"name":"John",
"age":28
},
"two":{
"name":"Jane",
"age":30
},
"three":{
"name":"Tom",
"age":28
}
} j := gojsonq.New().FromString(data)
ct := j.Where("*.age", "=", 28).Get() // or more nested like. "*.*.age"
fmt.Println(ct) |
This functionality seems extra; orthogonal (additional?) to the proposed patch. Are wildcards supported in This might be reasonable in future work; docs could illustrate the current behavior and its limits |
Issue #24 had an example of querying objects. In this particular case you need something like pattern matching/other good solution. I'm not sure what would be the use case of using |
the context is a single message object delivered in a queue (think pubsub or sns). In some cases it may be desirable to filterJSON. Use of the |
ping - any interest in merging this? |
As Thank you |
Change to enable queries on standalone objects. This makes queries like this possible: