-
Notifications
You must be signed in to change notification settings - Fork 17
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
Nested JSON items body_template in logzio_endpoint #70
Comments
For now I will be forced to create some proxy that accepts a flattened version of the JSON object (where nested paths are represented with dots), unflattens it and proxies it to the destination API. |
Hi @Tenchi2xh thanks for the feedback, we will check this issue and try to fix it. |
@Tenchi2xh version 1.5.0 is out and should fix this issue. |
Hi @Tenchi2xh did v1.5.0 fix the issue for you? |
@Tenchi2xh we're closing this issue, feel free to reopen if you have any further questions |
Hi sorry for the late reply :) Unfortunately I moved on from that project and cannot test this anymore, but I hope this will help somebody else! |
Hi ! I would like to do the following:
Since many endpoints have APIs which require nested objects, I am attempting to do that by nesting maps in maps for
body_template
.However, the type of
body_template
is hard set tomap of strings
which renders this task impossible (manually JSON-encoding the nested objects will result in a double encode with escaped characters):Would it be possible to change the type to
string
and let the users wrap the whole map with ajsonencode()
? That would enable users to use real world APIs and also as an added benefit allow for integer and float types.Thanks for your time
The text was updated successfully, but these errors were encountered: