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

Closure in Configuration file generate problem with config:cache #237

Closed
Belphemur opened this issue May 5, 2017 · 4 comments
Closed

Closure in Configuration file generate problem with config:cache #237

Belphemur opened this issue May 5, 2017 · 4 comments
Labels
duplicate A repeated issue or entry

Comments

@Belphemur
Copy link

Belphemur commented May 5, 2017

Laravel can't cache a closure correctly when in the config file.

The user->resolver would be better to a method of a class and use the container to call it than put a closure into it.

As a closure, laravel can't cache it.

Ps: I didn't see any warning about this in the documentation.

@quetzyg
Copy link
Contributor

quetzyg commented May 5, 2017

Not wanting to sound like a jerk, but did you at least made the effort to read the documentation or search for similar issues?

Thought so...

@quetzyg quetzyg closed this as completed May 5, 2017
@Belphemur
Copy link
Author

@quetzyg Darn, I missed the troubleshooting part.

Sorry ...

@scs75
Copy link

scs75 commented Jun 13, 2017

This totally screws up the the installation process.
Putting closure in config file is utter misdesign. A config file should be a declarative thing, not a functional process. Remnant of spaghetti php.

@quetzyg
Copy link
Contributor

quetzyg commented Jun 15, 2017

dyer

Can you, @scs75 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate A repeated issue or entry
Projects
None yet
Development

No branches or pull requests

3 participants