-
Notifications
You must be signed in to change notification settings - Fork 97
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
Permit .json and .ini suffixes on config files #82
Comments
It would be nice if YAML is supported as well - just like with |
I think file extentions is reasonable. I do not want to add yaml, but you can already use a custom parser (see the docs) already. Currently, Perhaps the way to do this would be to put an object Looking back I think that parsing one file as a variety of formats was a mistake. And the worst part, is I don't even know how many people are using ini! but I would if you had to explicitly set it, because I'd be able to look at the code of modules that depend on |
if you want to have backwards support for a default parser, use empty string as a key: (we'd have to handle that case specially, without adding the |
This adds support for the file extensions and for parsers by specific extension. All tests pass and a new one was added to test the extensions.
I made a pull request for the solution you were talking about @dominictarr, #85. |
Since this has appeared inactive, I have rewritten this module from the ground up as my own rc2. The loaders are fully configurable, and asynchronous. I plan on maintaining this module and reviewing PRs as well. |
rc
is awesome!It's a tiny thing, but it would be great if the config file logic would permit
.json
and.ini
extensions. In other words, looking for.${appname}rc
,.${appname}rc.json
or.${appname}rc.ini
in all the usual places.Definitely helps with triggering syntax highlighting in your editor of choice.
This idea was mentioned in #71, but since the scope of this feature request is far smaller in scope, I've opened it as a separate issue.
The text was updated successfully, but these errors were encountered: