[BUG] Selecting a JSON object in an Action Node request body does not deseralise object
kss-fluency opened this issue · comments
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
-
Go to Workflow
-
Create e. g. Contract Event Trigger Node and configure it
-
Create e. g. HTTP Action Node and configure it
-
Go to HTTP Action Node -> Input Parameters -> Body and select an object (such as
{{ContractEventTrigger_0[0].data.logs[0].eventFragment
in the following example
-
Test the node
Expected behavior
A deserialised object is being sent by an Action Node.
Screenshots
A Object object
string is being sent be an Action Node.
Setup
- OS: Ubuntu
- Browser Chrome
Additional context
Local deployment from the master
Any plans to fix that? I am happy to shoot a PR myself if I get some instructions on how to go about that.