Skip to content
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

Remove extensions feature flag #5365

Closed
rak-phillip opened this issue Aug 18, 2023 · 6 comments · Fixed by #7658
Closed

Remove extensions feature flag #5365

rak-phillip opened this issue Aug 18, 2023 · 6 comments · Fixed by #7658
Assignees
Milestone

Comments

@rak-phillip
Copy link
Contributor

rak-phillip commented Aug 18, 2023

In nuxt/vue configs, we specify a feature flag for extensions. This could be removed, as the feature is released in production.

          For a follow-up: we should remove this. (But not in this PR.)

Originally posted by @mook-as in #5287 (comment)

@jandubois
Copy link
Member

This seems to refer to this feature flag:

featureDiagnosticsFixes: process.env.RD_ENV_DIAGNOSTICS_FIXES === '1',

This seems to be used to modify the behaviour of the Diagnostics page.

I don't understand what is meant by "is released in production". It seems to be disabled by default.

So should we enable it by default and get rid of the flag? Or are the fixes not needed, because we did not enable them?

I'll put this into the next milestone solely to find out what we need to do, not to necessarily make the change right away.

@rak-phillip
Copy link
Contributor Author

@jandubois I think this issue had to do with the featureExtensions environment variable. It's a constant that always returns true. I think this is what I meant by "the feature is released in production" - the flag initially existed to allow for toggling extensions features during development.

@jandubois
Copy link
Member

think this issue had to do with the featureExtensions environment variable.

Ah, ok, my bad. So that would be just deleting this variable everywhere, right? I will do this myself.

Do you remember what RD_ENV_DIAGNOSTICS_FIXES is for? Is this work-in-progress that was abandoned? Or why is it not enabled by default?

Don't bother researching it, if you can't remember; I can run git blame to see what it relates to.

PS: I don't know why I have closed this issue; that was unintentional. 😄

@jandubois jandubois reopened this Oct 18, 2024
@rak-phillip
Copy link
Contributor Author

Do you remember what RD_ENV_DIAGNOSTICS_FIXES is for? Is this work-in-progress that was abandoned? Or why is it not enabled by default?

I would need to do the same git blame to refresh my memory for this one. 😆

@jandubois
Copy link
Member

I would need to do the same git blame to refresh my memory for this one. 😆

Thanks, in that case I'll do it myself.

@jandubois
Copy link
Member

Do you remember what RD_ENV_DIAGNOSTICS_FIXES is for? Is this work-in-progress that was abandoned? Or why is it not enabled by default?

It comes from acf8205 and is not something that should be enabled; it is unrelated to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants