Move env function to Support component - #19409
Merged
taylorotwell merged 1 commit intoMay 30, 2017
Merged
Conversation
Contributor
|
@mloberg I would suggest keeping this as-is, and create a third-party package for your personal use. If we started moving functions, probably that helpers file would become empty 😉 |
Member
|
I'm fine with moving this one because I don't think it really foundational to the framework. |
Contributor
|
@mloberg great work! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I find myself pulling in illuminate/support on projects (even non-Laravel projects). I really like the env function, but it's in Foundation instead of support, so I end up copying the function over to the project rather than having to pull in another package that I won't use anything else from.