-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Automatically require any files in app/config/initializers #59
Comments
Excellent idea. Also maybe for handlebars helpers. What about putting them directly into |
It doesn't matter too much to me where they go, just that they get loaded automatically. That said, I personally would prefer to keep the configuration related things inside |
I like this idea but I'm also coming from a Rails background. I haven't run into this yet but are there ever situations where you would want to require initializers in a specific order? Would this still be configurable? |
Initializers have their own ordering mechanism with the "before" and "after" property. Pretty cool actually. I'm for omitting the config folder because initializers are the config themselves. |
@rjackson closing in favor of a PR |
👍 I tried to naively |
Any updates on this? |
@zonak I'm planning to take a stab at it today |
Currently there is no automatic way of getting an initializer to run for you. I'm proposing to have any modules in the registry that start with
app/config/initializers
be required upon startup within the app.js (and start_app.js testing helper).I can implement this fairly easily if y'all agree.
The text was updated successfully, but these errors were encountered: