laravel/laravel — comment on commit f41717dcb195ae3bc400e8da660ae7410b2204fe
File:  line 0
By sparksp:

The only problem with putting that in the bundle config is that it's
up to the **app developer** to set it correctly not the _bundle
developer_. All the other config options are config for the app
developer (location, handles, auto). I guess choosing not to include
it is a choice for the app developer, as long as they know the
consequences.

On Sun, Feb 19, 2012 at 12:57, Taylor Otwell

wrote:
>
> I think it might be nice to have a "namespace" option in bundle config. That way we don't have to do all that guessing in auto-loader. I'll add it.
>
> On Feb 19, 2012, at 5:v28 AM, Phill Sparks wrote:
>
> > Why? I liked this feature! Now you have to start eloquent (and others) before you can use them - I'd rather not ('auto' => true) these - that's not the point. And having to Bundle::start('eloquent') in every model just isn't elegant.
> >
> > Do you have a suggestion for how to register bundle namespaces?
> >