String arguments get caught with comment filtering.

Question

String arguments get caught with comment filtering.

HunterJKI opened this issue 3 years ago · 2 comments

I had a use case where I wanted to send a path as a state machine argument, and for ...reasons... the files had # symbols in them. These get truncated out by the comment filter, and I don't think there is a way around it short of writing a specific character replacer.

Answer 1 · 2022-03-02T21:29:46.000Z

Here is an example with specific url style encoding, this works but would be nice to have a general solution with escape characters.

Answer 2 · 2022-03-03T09:15:30.000Z

A possible general solution is to use base64url encoding for the parameter. This avoids all possible control characters except '_' and '-'. I have base64url functions in JSONtext if anyone wants to copy them.

If fact, one should be able to flatten any datatype and then base64url encode, and thus be able to send any datatype as a parameter, not just paths.