[Bug][config-ui?] Issue with Incorrect URL Path Conversion in DevLake

[KelvinVenancio]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

I have identified an issue within DevLake's URL handling where the character "/" for Project name is not being properly converted to "%2F" as it should be. This problem is causing DevLake to interpret a path that doesn't actually exist, leading to incorrect behavior and unexpected results.

When attempting to use a URL containing the "/" character, DevLake fails to encode it correctly as "%2F", which is the standard URL-encoded representation for a forward slash. Consequently, the application is unable to correctly interpret and route requests that involve this character in the URL path.

What do you expect to happen

I expect that when using the DevLake application Projects with "/" on the name, any occurrence of the "/" character in the URL path should be correctly encoded as "%2F" according to standard URL encoding rules. This proper encoding will enable DevLake to accurately interpret and route requests involving URLs containing the "/" character.

How to reproduce

To reproduce the issue, follow these steps:

1. Create a new project with a "/" character in its name.
2. Add a "Data Connections" component to the project.
3. Click on "Edit Data Scope and Scope Config" for the added component.

The error occurs in step 3, as illustrated by the images below:

Upon performing these steps, you should observe the incorrect behavior where the DevLake application fails to properly handle the "/" character in the URL, leading to an error or unexpected result. This reproduction will help demonstrate the problem and assist in identifying the root cause of the issue.

Anything else

Note that in image 3 above, the access worked correctly after I corrected the URL manually by adding the code for the character "/".

Version

v0.18.0-beta7

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[Startrekzky]

I think this is a bug.

[mintsweet]

Hi, @KelvinVenancio. Thank you for your report.
But I didn't catch the error from your screenshot. Can you provide the error screenshot?

[KelvinVenancio]

Hi @mintsweet <https://github.com/mintsweet>, the error is on the second image: blank screen. You need anything else? Thank you. Em ter., 29 de ago. de 2023 às 23:10, 青湛 ***@***.***> escreveu:

…

Hi, @KelvinVenancio <https://github.com/KelvinVenancio>. Thank you for your report. But I didn't catch the error from your screenshot. Can you provide the error screenshot? — Reply to this email directly, view it on GitHub <#5976 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABL6VW4ZH4RYXVU2DHUH3ODXX2OH3ANCNFSM6AAAAAA4C4COD4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mintsweet]

Hi, @KelvinVenancio, sorry for missing the error image. I will fix it today.