Skip to content
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

Use a new file extension #5

Open
elbrujohalcon opened this issue Jul 29, 2015 · 2 comments
Open

Use a new file extension #5

elbrujohalcon opened this issue Jul 29, 2015 · 2 comments
Assignees

Comments

@elbrujohalcon
Copy link
Member

I would recommend something like *.nconf to distinguish from *.config files.

@igaray
Copy link
Member

igaray commented Aug 5, 2015

The main entry point to nconf's code is supplied with a filename which is passed to file:consult, i.e.

name_all() = string()
           | atom()
           | deep_list()
           | (RawFilename :: binary())

Should nconf enforce the extension?

@elbrujohalcon
Copy link
Member Author

No, it should only be consistently mentioned in the documentation / README.md file, @igaray

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants