Skip to content

Conversation

@Emyrk
Copy link
Member

@Emyrk Emyrk commented Jan 13, 2023

Currently the experimental flag is only set on Enterprise routes via updateEntitlements.

In the free version, Experimental is on the api config and never set.

Dropping the unused boolean.

@Emyrk Emyrk requested a review from kylecarbs January 13, 2023 19:01
@kylecarbs
Copy link
Member

Hmm, why add this if it's unused? Feels odd.

@Emyrk
Copy link
Member Author

Emyrk commented Jan 13, 2023

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.

@Emyrk Emyrk changed the title chore: Pass through experimental config chore: Drop unused Experimental flag from api options Jan 13, 2023
@johnstcn
Copy link
Member

Would it instead make more sense to refactor the experimental flag from bool to []string so that multiple experimental options can be enabled or disabled independently?

@Emyrk
Copy link
Member Author

Emyrk commented Jan 17, 2023

@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.

@Emyrk Emyrk closed this Jan 18, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jan 18, 2023
@Emyrk Emyrk deleted the stevenmasley/pass_through_experimental branch February 3, 2023 19:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants