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
In Git repositories, it's common to use LF (\n, "Unix-style") line endings for better cross-platform compatibility (see Lombiq/Open-Source-Orchard-Core-Extensions#65). The problem is that with .cs files, if we have LF line endings instead of CRLF (\r\n, "Windows-style") then roslyn will emit several false-positive IDE0055 warnings. There is a workaround of making only the .cs files CRLF as described in the above-linked issue. We have applied it to this repo and its submodules during OSOE-49.
What needs to be done?
Once the analyzer is fixed, the *.cs text eol=crlf rule should be removed from all .gitattributes files and then all .cs files should be renormalized to LF using the same steps described in the issue description of OSOE-91.
This is our follow-up issue once dotnet/roslyn#55526 is fixed.
What's the problem?
In Git repositories, it's common to use
LF
(\n
, "Unix-style") line endings for better cross-platform compatibility (see Lombiq/Open-Source-Orchard-Core-Extensions#65). The problem is that with .cs files, if we haveLF
line endings instead ofCRLF
(\r\n
, "Windows-style") then roslyn will emit several false-positive IDE0055 warnings. There is a workaround of making only the .cs filesCRLF
as described in the above-linked issue. We have applied it to this repo and its submodules during OSOE-49.What needs to be done?
Once the analyzer is fixed, the
*.cs text eol=crlf
rule should be removed from all .gitattributes files and then all .cs files should be renormalized toLF
using the same steps described in the issue description of OSOE-91.Jira issue
The text was updated successfully, but these errors were encountered: