API Endpoints Require Manual Encoding of Special Characters in URLs

[SimonHenz97]

Description:

Several API endpoints require the use of special characters in their URLs, which necessitates manual encoding before these URLs can be used with YAADE. This manual step seems counterproductive and could potentially lead to errors or inconsistencies.

Example:

The following URL:

${host}/CategorySet?$filter=( McatId eq "/HSEPA" )&$select=CatText,CatId

must be manually converted to:

${host}/CategorySet?$filter=(%20McatId%20eq%20%27/HSEPA%27%20)&$select=CatText,CatId

If the URL is not properly encoded, the API request fails.

Expected Behavior:

It would be more efficient if YAADE could automatically handle the encoding of special characters in URLs, ensuring both the reliability of requests and user convenience.