-
Notifications
You must be signed in to change notification settings - Fork 29
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
refactor(app-shell): remove old feature flags #602
Conversation
'customerGroups', | ||
'projectSettings', | ||
'developerSettings', | ||
'projectSettingsChannels', |
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 went ahead and did a little clean up. These feature won't be untoggled and we should clean up our used flags in the MC then too.
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.
perfect!
it looks to me that I have to update this file as well, since I introduced 2 new feature flags?
No. Only if those features are ought to be accessible through Quick Access and their access is toggled. |
yeah I just realised that now. carry on 😗 |
fd3603c
to
4f76f71
Compare
}, | ||
featureToggles.customApplicationsSettings && |
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.
This was actually wrong. There is no flag like this and the flag requested is called differently. Hence, quick access for custom app settings was never working to how I see it.
Summary
I assumed flags are passed from the app but quick-access connects to them itself. Another case for types casue the prop-types are not followed through to the
create-commands
-fn.