[GitHub] [jmeter] vlsi commented on issue #5035: Parameterized and non parametrized strings handle \ differently, so HTTP request body with \ sends a completely different value when ${..} added

["vlsi (via GitHub)" <gi...@apache.org>]

vlsi commented on issue #5035:
URL: https://github.com/apache/jmeter/issues/5035#issuecomment-1555597354

   Non parameterized strings do not process `\` as a special character, while parameterized strings uses a special character to escape `$`. For instance, in case the user wants to send `$` they use `\$`.
   
   That is the "proper" way of adding parameterization is to double every `\` before adding `$`. Of course it is not easy, and we could add a button to escape/unescape strings. However, that workaround shound help.
   
   An alternative option would be treating only `${` as a special sequence outside of the parameterization. In that case, there will be no need adding slashes, howewer sending `${` would require something like `${$}{`.
   
   Apparently, it would help if we implement syntax highlight. Then the users will see that `\\` has a special meaning in case parameterization is used.
   
   The issue is similar to https://youtrack.jetbrains.com/issue/KT-2425/Provide-a-way-for-escaping-the-dollar-sign-symbol-in-multiline-strings-and-string-templates
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org