Closed mikevrind closed 9 years ago
Hmm could be. But I'm not really super happy by having to add that to all packages.. Taylor said he was going to look at it soon.
Is this how Laravel 5 is handling config namespaces now? I haven't had much luck in my investigations. Seems like a large step down from the addNamespace method.
@barryvdh @rcrowe This is about as good as it gets. Loading onto the resolved config repository is entirely the developers responsibility now. My buddy confirmed it at a meetup with Taylor last night as well.
I would say merge 'er up and let's get this package updated! VCS's in composer make me itchy ^_^
Okay, I'll guess we'll continue on a 0.7x branch with L5 support only? Instead of fallbacks etc.
Sounds like a sensible decision
Started in #166 / 0.7 branch but the tests need a lot more work. Closing this in favor of the PR.
I can dig it
I know I know... L5 is still in development. But maybe it would be usefull to add a little fallback in the SP for L5 support just as @barryvdh did with his debugbar?
The current SP isn't compatible with L5.