You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using dynamics with unknown content (eg. SMS message content), crafting HTTP requests with a JSON body isn't reliable, as you cannot be sure that the string is properly escaped.
Describe the solution you'd like
I would like to be able to post-process a given dynamic to make sure it's properly quoted for a given application (eg. JSON quoting, SQL sanitization, etc.)
Describe alternatives you've considered [optional]
An easy alternative could be to write a termux script that will sanitize my string(s) and forward them instead of doing the sanitization in Easer. Perhaps I could even fire an event to have easer pick up the resulting string and continue in a different script.
I'm quite new to Easer, so I may be overlooking the "right" way to have a pipeline exit/re-enter an Easer script. I'm not sure if this sort of feature should be considered out-of-scope.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When using dynamics with unknown content (eg. SMS message content), crafting HTTP requests with a JSON body isn't reliable, as you cannot be sure that the string is properly escaped.
Describe the solution you'd like
I would like to be able to post-process a given dynamic to make sure it's properly quoted for a given application (eg. JSON quoting, SQL sanitization, etc.)
Describe alternatives you've considered [optional]
An easy alternative could be to write a termux script that will sanitize my string(s) and forward them instead of doing the sanitization in Easer. Perhaps I could even fire an event to have easer pick up the resulting string and continue in a different script.
I'm quite new to Easer, so I may be overlooking the "right" way to have a pipeline exit/re-enter an Easer script. I'm not sure if this sort of feature should be considered out-of-scope.
The text was updated successfully, but these errors were encountered: