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
Disable and enable strategies - frontend #3582
Conversation
Tymek
commented
Apr 21, 2023
•
edited
edited
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
Signed-off-by: andreas-unleash <andreas@getunleash.ai>
filter out disabled strategies Signed-off-by: andreas-unleash <andreas@getunleash.ai>
filter out disabled strategies by default. return disabled strategies for the UI and the playground Signed-off-by: andreas-unleash <andreas@getunleash.ai>
133d25d
to
600fe25
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.
Very nice.
A few non blocking comments:
- I'd add the 2 new flags to our hosted instance (even before you start work on a new feature)
- Disabling last strategy doesn't disable a toggle - is it by design?
- For all new code I write I try to increase test coverage. Maybe after merging this PR try to add at least one cypress tests for the Change Request user journey?
- In future PRs I'd split logical changes like changing a title and disabling strategy at least into 2 separate PRs if not more. It makes it easier for the reviewers.
@kwasniew we agreed to avoid adding Cypress tests for the use cases that are not essential to the core functionality of the application. These tests tend to have a high maintenance overhead and can be flaky, which diminishes their value. |