- Notifications
You must be signed in to change notification settings - Fork1k
chore: Drop unused Experimental flag from api options#5715
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Hmm, why add this if it's unused? Feels odd. |
Good point. We return the entitlements in the enterprise route for the UI to consume. I just noticed this when trying to implement a backend experimental feature. I'll just drop it for now. |
Would it instead make more sense to refactor the |
@johnstcn It would be nice to support that kind of behavior. This PR just drops the unused flag so no one tries to use it and realizes it does nothing. A future PR can re-add this functionality in a way that works. |
Uh oh!
There was an error while loading.Please reload this page.
Currently the
experimental
flag is only set on Enterprise routes viaupdateEntitlements
.In the free version,
Experimental
is on the api config and never set.Dropping the unused boolean.