-
Notifications
You must be signed in to change notification settings - Fork 928
chore: add 'classic_parameter_flow' column setting to templates #17828
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
Conversation
Defaulting to true
@Emyrk Do you mean we are removing the dynamic parameters experiment next week? |
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.
a boolean named classic_parameter_flow
isn't very clear. I think use_classic_parameter_flow
conveys intent much better.
We might be. I forgot it depends on the smoke test |
4ada164
to
a90c6a0
Compare
…_dyn_param_toggle
In terms of design I think we could:
Feel free to ignore them if you think they are out of this scope. 👍 |
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.
FE changes are good 👍. I just left a comment related to a few design concerns.
I am going to leave this as our other checkboxes are like this. I reduced the description text, so it should look a bit better being smaller.
👍 |
We are forcing users to try the dynamic parameter experience first. Currently this setting only comes into effect if an experiment is enabled, however we are removing that experiment very soon.
So I am just going to show the setting, rather than have to add logic I will remove before the next release.
What this does
The checkbox gives the template admin to opt a template out of the dynamic parameters experience, and use the existing form. We expect some bugs, so if a template has some issues, turning this off template wide prevents the end user from hitting any errors to begin with.
This does default to the new experience, as we want to force the template admins to try dynamic params first.
Regardless of this checkbox, the user can manually switch experiences at will.