Doesn't FluentAssertions have an option to ignore differences in line breaks?
I couldn't find it.
The build.cmd just invokes dotnet, so it should be easy to translate to bash.
It's true. Even tried this approach yesterday, but I had only a core 3.0 preview on my WSL, so things did not go well!
MatchEquivalentOfwill ignore ends of lines and case, which is close. Looking to see if we can turn on only one of those switches!
autocrlfprobably comes into play here too
NormalizeLineEndings-type extension method or specialized FluentAssertion comparers. The latter is probably slightly cleaner as we don't have to pollute
string, but it would just be in the tests, and I think not such a big deal.
Okay. Customized FluentAssertions it is, not unlike
@LukeMarlin, is this something you're comfortable with/interested in? I'd be happy to work on the change if not, but I realize it's blocking you, so maybe the timing works better if you investigate?
Whatever you prefer.
System.Environment.NewLine. Or is this even necessary? I've been out of the Mac game for a while. Bare
\rs have gone out of fashion, right?