-
Notifications
You must be signed in to change notification settings - Fork 87
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
[#2] Implemented elvis for console usage #9
Conversation
…es under specified directories.
…ses and adding docstrings.
…e status to console output.
%%= ok | ||
``` | ||
|
||
`Config` which should have a valid format. Since this is a project under development what is a valid format is still a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This paragraph doesn't sound right to me, syntactically speaking.
{ok, binary()} | not_found. | ||
src(_Config, FilePath) -> | ||
case file:read_file(FilePath) of | ||
{error, enoent} -> not_found; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're returning something, instead of throwing an exception (which is what I would've done :P). It should be enoent
so that it's consistent with similar errors from Erlang/OTP
…uxiliary test functions to a test module. Replaced not_found for {error, enoent}.
…failure to README.
[#2] Implemented elvis for console usage
Also added tests and a description in the README on how to configure and use elvis form the Erlang shell.