_encodeDecode(string, mode,output variable) where mode is: BASE64_ENCODE BASE64_DECODE HEX_ENCODE HEX_DECODE
Implementation provided with https://github.com/apache/jmeter/pull/530 I wonder, whether one function to encode and decode with a switch is a good design. This is probably driven by the notion that too many functions are already available. This might be a good starting point to discuss how we can organize functions, that there are not too many functions visible at the same time (in the docs, in the code, in ...).
I agree with Felix, we should not combine unrelated functions under a single name. How base64 is related to hex? What if the user wants upper case or lower case hex? If the listed base64/hex encode/decode are required in core (?), they should be 4 distinct functions rather than a single one. On top of that, it is not clear why input of encodeDecode is String. Typically base64 is used to encode byte[] rather than a sting.
Hello, I created this bugzilla a bit rapidly, when I further thought about it to implement it , it looked less useful particularly when decoding to binary. So I close it as is. Let's discuss this before Regards
I guess it is perfectly fine to have a bug id (so we can discuss it). However, I don't feel the feature is ready for implementation yet.
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4605