-
Notifications
You must be signed in to change notification settings - Fork 411
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: Environment creating state #4060
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
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.
The bug I originally reported is fixed, but we're introducing the same behaviour as in #4026. If the request fails or is blocked, the Create button will never be re-enabled and no error is displayed.
Approving anyway because it's better to need to refresh the page than to delete duplicated environments :)
@rolodato I've fixed the above in the PR |
Not sure if I'm looking at the correct deployment, but I can reproduce the same behaviour by blocking the request to clone an environment in https://flagsmith-frontend-staging-4x2teb60z-flagsmith.vercel.app/ : block.env.create.mov |
Ah yep I forgot that #4058 is yet to be merged, added the relevant fixes here too. |
I see the button correctly being disabled while the environment is being created, but I don't see an error visibly reported if blocking the request or trying to clone an environment while offline: create.env.no.error.mov |
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Disables create env button when creating
How did you test this code?