Skip to content

Make automatic .env load an opt-in feature rather than automatic #880

@felipecrs

Description

@felipecrs

Is your feature request related to a problem? Please describe.

So, as the conversation goes on in #845, it turns out to be very obvious that #845 was a breaking change which didn't receive a treatment of such (no major version bump, for example).

Describe the solution you'd like

So, in order to keep 2.x version tree clean, I would suggest we make the automatic .env load an opt-in feature, rather than on by default.

The user could optionally opt-in by setting a global configuration for direnv (which I'm not sure how that could be achieved, perhaps ~/.direnvrc?

Describe alternatives you've considered

We could simply bump direnv version to 3, but... in fact I think it would be a very welcome addition to let users decide whether they want to use this feature (which is super useful for me) or not (which seems to be breaking some users cases).

Additional context

None.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions