-
Notifications
You must be signed in to change notification settings - Fork 260
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
Create new feature form #936
Conversation
Signed-off-by: Boli Guan <[email protected]>
Thanks for the PR! @Fendoe is there a staging env that folks can play with? |
@xiaoyongzhu Blair will provide it tomorrow. |
Signed-off-by: Boli Guan <[email protected]>
Signed-off-by: Boli Guan <[email protected]>
@xiaoyongzhu please checkout this staging link: https://brave-moss-045d2ce00-25.eastasia.1.azurestaticapps.net |
@Fendoe I did some test and find a bug for unhappy path. To repro this, just create a feature with a name that already exists in project, the api responses 400 correctly but UI displays feature created successfully message. The expected behavior is UI should display the 400 error message returned from api to tell user detail error. |
Signed-off-by: Boli Guan <[email protected]>
Signed-off-by: Boli Guan [email protected]
Description
Resolves #488
How was this PR tested?
Does this PR introduce any user-facing changes?