You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows and Linux/macOS systems use different line-endings in files.
It seems like a good idea not to mix these in the same codebase.
Options
force - Force a choice, values can be unix or windows.
Reasoning
While this is not necessarily a concern for the correctness of your code, you should use a consistent style throughout your codebase.
Note: If you're using a formatter, this should already be taken into account by it.
Refactoring Proposal
elvis should warn about where differences are found (if no force consider the first occurrence as "the standard") and throw an error per file alone, not one per line.
Name
consistent_line_endings
Brief Description
Windows and Linux/macOS systems use different line-endings in files.
It seems like a good idea not to mix these in the same codebase.
Options
force
- Force a choice, values can beunix
orwindows
.Reasoning
While this is not necessarily a concern for the correctness of your code, you should use a consistent style throughout your codebase.
Note: If you're using a formatter, this should already be taken into account by it.
Refactoring Proposal
elvis
should warn about where differences are found (if noforce
consider the first occurrence as "the standard") and throw an error per file alone, not one per line.Origin (#281)
Inspired by Credo's https://hexdocs.pm/credo/Credo.Check.Consistency.LineEndings.html.
The text was updated successfully, but these errors were encountered: