Hi @pradeeban ,
While testing some of the server actions, I noticed that requests can fail if folder or workflow names contain special characters (like spaces, &, ?, or newlines).
Currently, the URLs for server actions like build, clear, and library are built using raw string concatenation. This means if a user names their folder "my project" (with a space), that raw space gets injected directly into the URL, resulting in a malformed request that the server can't parse correctly.
Any dynamic path segments or query values should be properly URL encoded before the requests are fired. This ensures that the app stays robust and requests remain valid, regardless of what the user names their files or workflows.
Fix
The fix is pretty straightforward, just need to wrap the dynamic variables in standard URL encoding functions before appending them to the base URL string.