-
Notifications
You must be signed in to change notification settings - Fork 415
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
feat: Use environment feature state instead of fetching feature states #4188
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.
I've tested this and it looks good to me 👍 . Since it's quite a critical change, I'd love to get another pair of eyes on it as well, although I guess the E2E tests will cover this part of the app significantly.
@kyle-ssg why we don't use the RTK here? |
It’ll be very difficult to migrate this given how integral and widely used it is. Though I did make versioning use it to make it easier when we do. |
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. Also, the functional tests are working.
…ature_state # Conflicts: # frontend/common/stores/feature-list-store.ts
Docker builds report
|
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
In order for the feature list page to function, it needs access to the features and feature states.
Prior to this the frontend got all feature states when fetching features and matched them up. Now that the backend returns the feature states in the features, this PR adjusts the Frontend to use that rather than fetching them.
Resolves #3301
How did you test this code?