-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Workspace name can't contain uppercase #361
Comments
PS: Should I also fill a feature request to have Workspace name supports spaces and uppercase letter at first char? |
@noraj It's ok to leave it here. We may add support for upper on first char. For white spaces we need to add a slug, since workspace name is used on the api urls. |
@llazzaro Or you can associate a UID to each workspace and use the UID in the API. The UID is unique and never change, then you can associate whatever name at it and even rename the workspace. |
We have been discussing this issue with the dev team. The problem of using UID is backwards compatbility. The restriction on the workspace name cames from the couchdb era, where the workspace name was the couchdb database name. |
Description
An alert tells me
Error: Workspace name can not contain white spaces or start with uppercase.
when I try to name the workspacetestWorkspace
buttestWorkspace
doesn't start with an uppercase and contains no white-space.This may due to a bad regex matching white-space at any position instead of checking the first char only.
Issue Type
Faraday version
Faraday v3.7.0
Component Name
I don't know.
Steps to reproduce
testWorkspace
Expected results
I could name a workspace
testWorkspace
.Debugging tracebacks (current results)
It is more a bad implementation than a bug so there are not debug logs.
Screenshots
Environment information
Configuration files
No needed. I changed nothing pure default.
OS
🤣
/etc/lsb-release
? The standard file is/etc/os-release
. #362The text was updated successfully, but these errors were encountered: