-
Notifications
You must be signed in to change notification settings - Fork 11
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
Persistent sessions name limitations #796
Comments
Hi @ccarouge, Thank you for submitting this issue. I agree, there are some things with Since I don't know the exact current limitations of But I think the Does it make sense to you? |
Yes, it makes sense to me. I'm not sure I agree with not warning users of the limitations we already know but that's not my call. |
Yes, I understand your concerns. The issue is that I don't know what limitations on characters are in place. |
I would put a warning against using any special character and using a single "word" name, CamelCase can be used to separate words. Example: Persistent session names accept a limited set of characters. We recommend using only alpha-numeric characters without any space in the chosen name. CamelCase can be used to identify separate words within the name. E.g: |
Description
I've just started my first persistent session today. I tried calling it "test_199b" and got:
It seems persistent session names have limitations on valid characters, it might be good to warn users about it in the instructions.
I don't know what the limitations are, it might be only alpha-numeric characters...
Close Criteria
Information in the instructions about valid characters for persistent session names.
The text was updated successfully, but these errors were encountered: