Url configuration redirect url wilcard not saved properly

[sagarchoudhary96]

Describe the bug

i'm trying to add a wildcard for redirectUrI in supabase auth dashboard, http://localhost:3000{**,/**}:

Example with the tool mentioned in subabase doc

when i add it to the dashboard it is getting saved as two url.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to 'dashboard > auth > url-configuration'
2. try adding http://localhost:3000{**,/**}

Expected behavior

it should be added as one url

[MildTomato]

@kangmingtay @J0
we have an issue here with keeping urls in a comma separated string.

Not sure we can safely separate the string on client, or if even the gotrue middleware can?

[J0]

Oh the URI_ALLOW_LIST environment variable which maps to the list of valid redirect urls lives on the server and we perform checks there.

By

separate the string on client, or if even the gotrue middleware can?

Were y'all hoping to pass the uri list to the server on a parameter in the supabase-js client library method which can then be split by either the middleware on GoTrue or the Supabase-js lib? Taking a guess here, because I'm not fully certain.

Do y'all mind also sharing a high level overview of the issue with storing comma separated string? Would be helpful for us as we explore alternatives

[MildTomato]

@J0 they are using the redirect "http://localhost:3000{**,/**}" but the comma in it forces the FE to split the comma separated string wrong.

I assume on server you are just doing something like redirects.split(',') ?

Would it not make more sense these are stored in an array anyway?

[kangmingtay]

@MildTomato yeah you're right, it's one of the disadvantages of the library we're currently using to read the environment file for gotrue