-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Save and Exit: Add FF and update links #6852
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
base: develop
Are you sure you want to change the base?
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
d5107aa
to
3444f67
Compare
2aa7125
to
cc4c1a2
Compare
|
||
@Toggle.DefaultValue(DefaultFeatureValue.FALSE) | ||
@Toggle.InternalAlwaysEnabled | ||
fun saveAndExitSerpSettings(): Toggle |
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 kinda feel you want another FF specific to using the new settings activity, appreciate that code is in the next PR though.
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 suppose since we're getting rid of the Save and Exit button I guess it should be called something like SettingsWebView
but why would we need another FF?
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.
Yeah agreed, I'd rename to settingsWebView. The second feature flag is less relevant now but I left a message on the other PR explaining my reasoning (I think we can still do it).
This reverts commit 04a1c4a.
cc4c1a2
to
e3e06cb
Compare
Task/Issue URL: https://app.asana.com/1/137249556945/project/1202552961248957/task/1211395150174608
Description
This PR adds a FF and updates the private search and duck.ai settings links.
Steps to test this PR
QA-optional