Skip to content

Dotenv: Unused Loader instance in __construct #210

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

Closed
wants to merge 1 commit into from

Conversation

jrchamp
Copy link
Contributor

@jrchamp jrchamp commented Nov 18, 2016

loadData() will always create a Loader instance, so creating one in Dotenv::__construct() is only useful for Validate.

Hopefully travis agrees.

loadData() will always create a Loader instance, so creating one in
Dotenv::__construct() is only useful because it is currently required
for Validate to work before calling load() on a real file.
@GrahamCampbell
Copy link
Collaborator

Hmm. Not sure this is the best fix actually.

@GrahamCampbell
Copy link
Collaborator

I think we have a more fundamental design problem here.

@jrchamp
Copy link
Contributor Author

jrchamp commented Nov 28, 2016

Completely agree that this is not the best fix. This only makes it more clear what is happening whereas right now, it's somewhat misleading. Feel free to close this out when you have a better solution. If you can, please link to that better solution here.

@vlucas
Copy link
Owner

vlucas commented Dec 14, 2016

Just merged #215 which fixes this problem in loadData.

@jrchamp
Copy link
Contributor Author

jrchamp commented Dec 14, 2016

Thanks @vlucas, closing.

@jrchamp jrchamp closed this Dec 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants