Custom command is not finding models about lithium HOT 7 CLOSED

Could this be related to issue #21?

from lithium.

Cheers @gwoo seems like it is the same issue, using Environment::set in the environment bootstrap solved this for me.

Maybe having the default environment when using the console set to development, then being able to add an environment flag might be a good way of dealing with this?

from lithium.

@gwoo what about setting --env automatically to "development" and let the user override it if needed? I did it this way for the routes command but we could easily refactor that some levels up - what do you think?

from lithium.

This is how the rails console works, I think it is good, I am just adding some code to the environment detector now to show this working.

Cheers

from lithium.

+1 for setting --env automatically to "development" and notify the user

from lithium.

Added pull request to fix this on issue #61

from lithium.

Awesome, thanks @mackstar.

from lithium.