-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add common examples / use cases in a examples folder #76
Comments
Good idea ! |
@alesc what is your upstream header property |
@diegolucasb Can confirm this issue. Content-Encoding is gzip. |
Sorry for the late response, found out just now. Try sending the header |
Hi, {
"Classified": [
{
"ItemID": "1111",
"Something1": {
"Field1": "value"
... more keys:values
},
"Something2": {
"Field1": "value"
... more keys:values
}
}
]
} "Classified" is a list of many items. I want to transform this response to: {
"Classified": [
{
"ItemID": "1111",
"Zones": [
{
"Name": "Something1",
"Field1": "value",
... more keys:values
},
{
"Name": "Something2",
"Field1": "value",
... more keys:values
}
]
}
]
} Would you please help out with this? I am not also sure if your plugin can handle such structure. Thank you. |
The README.md says:
which is a bit vague and it would be helpful if this statement is accompanied with example(s) of such times the "Sometimes" refers to. |
Issue Description
At the moment, we have just simple examples but by using the plugin for half a year, we came across some complex use cases that would be worthy to share.
Expected Behavior
We should have more examples.
Checklist
The text was updated successfully, but these errors were encountered: