doc unexpected-line-ending-format

[hofrob]

Type of Changes

	Type
✓	📜 Docs

Description

Add doc for unexpected-line-ending-format / C0328

Refs #5953

[codecov]

Codecov Report

Merging #8255 (9625cb8) into main (32e1545) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8255   +/-   ##
=======================================
  Coverage   95.46%   95.46%           
=======================================
  Files         177      177           
  Lines       18691    18698    +7     
=======================================
+ Hits        17843    17850    +7     
  Misses        848      848           

Impacted Files	Coverage Δ
pylint/checkers/variables.py	97.30% <0.00%> (+<0.01%)	⬆️
pylint/pyreverse/main.py	93.87% <0.00%> (+0.54%)	⬆️

[hofrob]

It's not that easy to commit an actual file with CRLF if all your tools are trying to smart and help you "do the right thing" 😬

[Pierre-Sassoulas]

Yes you'd need to modify our .gitattributes for that. But it's impossible to see that you did the right thing while reading the doc though :) Maybe something that don't need a bad/good that we could handle in #7897 with a nice story about the meaning and history of CRLF and type printer.

[hofrob]

Right now it's correct, but you're right, this is not visible in the docs. I added inline comments like in the missing-final-newline docs.

I'm thinking about adding an explanation in a details.rst.

[Pierre-Sassoulas]

Might want to link this https://stackoverflow.com/a/6521730/2519059 and this https://stackoverflow.com/a/10855862/2519059 in related too.

[hofrob]

Ok, those links are awesome and have all the info needed (I think). I added those and a link to the awesome gitattributes template repo to related.rst now.

[hofrob]

I don't get it. It worked yesterday. Now it doesn't anymore. The bad.py file has CRLF when I check it out locally. But something along the way replaces them with LF again.

🤷