-
Notifications
You must be signed in to change notification settings - Fork 22
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
fix: forbid creating several playgrounds with the same name #1016
Conversation
182aab2
to
e81476b
Compare
3d46fc8
to
1c9a3dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a weird feeling with isFreeName
I am not a native english speaker so I might be wrong, but I feel like isNameFree
sound better
Signed-off-by: Philippe Martin <phmartin@redhat.com>
Signed-off-by: Philippe Martin <phmartin@redhat.com>
Signed-off-by: Philippe Martin <phmartin@redhat.com>
Co-authored-by: axel7083 <42176370+axel7083@users.noreply.github.com> Signed-off-by: Philippe Martin <feloy1@gmail.com>
Signed-off-by: Philippe Martin <phmartin@redhat.com>
2d0db3b
to
115d536
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀 ! Thanks for the changes!
What does this PR do?
Raise an error when the user creates a playground with a name already used by another playground.
Screenshot / video of UI
playground-same-name.mp4
What issues does this PR fix or reference?
Fix #782
How to test this PR?