Closed basaran closed 3 months ago
Hi @basaran, the deny
, allow
, or even the flatmap
functionality reserves the dot to access nested objects (there are more components like this). There is no special syntax for working with literals containing dots, so this functionality is not supported in the community edition.
On the other hand, the mapping
attribute does not support nested functionality, which is why you can work with literals with a dot.
You could implement the logic using allow
instead, or create an intermediate endpoint
thank you for the clarifications. Arigato.
Environment info:
Version: 2.6.0 Linux 6.7.7-1-MANJARO x86_64
Describe what are you trying to do: API I'm testing with returns some JSON keys with dots in them. For instance:
I am trying to deny it in the response.
But it doesn't work. I did confirm though, I can rename this field. Is there a special syntax I need to use to escape the dot or the at symbol when using deny?
Renaming works fine.