Adding url decoding function to extend template functionality in easegress builder filters about easegress HOT 5 CLOSED

URL decoding (encoding) is a common scenario in the traffic orchestration system. I suggest providing users with helper functions for use in builder filters or predefined filter options.

from easegress.

As far as I know, I can't find a better way to extend the template functions except make a new pr for it? So, if you like, feel free to make a pr for it and please make sure to update the corresponding documentation.

By the way, with newest easegress, you can simplify

{{.responses.DEFAULT.JSONBody.data | urldecode}}

to

{{.resp.JSONBody.data | urldecode}}

Please check https://github.com/easegress-io/easegress/blob/main/docs/07.Reference/7.02.Filters.md#template-of-builder-filters for more details.

from easegress.

As far as I know, I can't find a better way to extend the template functions except make a new pr for it? So, if you like, feel free to make a pr for it and please make sure to update the corresponding documentation.

By the way, with newest easegress, you can simplify

{{.responses.DEFAULT.JSONBody.data | urldecode}}

to

{{.resp.JSONBody.data | urldecode}}

Please check https://github.com/easegress-io/easegress/blob/main/docs/07.Reference/7.02.Filters.md#template-of-builder-filters for more details.

Thank you for your suggestion. I will create a pull request to address this issue by adding the 'urlQueryEscape' and 'urlQueryUnescape' template functions to the builtin extraFuncs .

from easegress.

#1194

from easegress.

#1194 I have implemented the 'urlQueryEscape' and 'urlQueryUnescape' template functions and added them to the builtin extraFuncs. You can now utilize them as follows:

{{.resp.JSONBody.data | urlQueryUnescape}}

from easegress.