Wappler could use this formatter on both the front-end and back-end. @Apple put in a feature request in 2024 for the front-end and it's not marked as implemented.
On the backend, using urldecode() does not work to completely decode the URI string. In v6.8, the formatter in string.js looks like:
urldecode: function(str) {
if (str == null) return str;
return decodeURI(String(str));
}
which fails to correctly decode a query parameter that has a reserved character in it:
; , / ? : @ & = + $ #
If we can't update the existing urldecode() formatter, can we get a new urldecodecomponent() formatter using: decodeURIComponent(String(str))