ChrisSamo632 commented on pull request #4756: URL: https://github.com/apache/nifi/pull/4756#issuecomment-854718192
> @ChrisSamo632 wow. The example that I gave of `Base64Decode` does in fact match the convention you used :) Generally we would use though such as escapeJson, unescapeJson. Just like we do in Expression Language. It is odd that Base64Encode / Base64Decode does not follow that pattern, but I think that's an oversight. > > Sorry, I realize it may seem like a bit of a quibble. But I definitely think that escapeJson / unescapeJson will be more intuitive for users. Especially since we already have an escapeJson / unescapeJson in Expression language. Reversing the order here I think would lead to a lot of confusion. @markap14 no big deal - I'll change the names again (but leave the base64 functions along as that would obviously not be backwards compatible for any existing flows!) -- 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. For queries about this service, please contact Infrastructure at: [email protected]
