Problem description
The Gherkin linting rules currently contain the following rule:
"new-line-at-eof": ["on", "no"],
This causes issues if the feature files are edited using the Github web browser, ultimately due to differences between Linux and Windows line endings.
Expected behaviour
The simplest solution is to remove this rule completely, and not care about which line endings are used in files
Alternative solution
The alternative is to enforce common line endings for all files, either project wide, or locally for each repository.
See https://docs.github.com/en/get-started/git-basics/configuring-git-to-handle-line-endings
Additional context
This problem is as old as MS-DOS itself
Problem description
The Gherkin linting rules currently contain the following rule:
"new-line-at-eof": ["on", "no"],This causes issues if the feature files are edited using the Github web browser, ultimately due to differences between Linux and Windows line endings.
Expected behaviour
The simplest solution is to remove this rule completely, and not care about which line endings are used in files
Alternative solution
The alternative is to enforce common line endings for all files, either project wide, or locally for each repository.
See https://docs.github.com/en/get-started/git-basics/configuring-git-to-handle-line-endings
Additional context
This problem is as old as MS-DOS itself