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
We have several places where we deal with linebreaks:
Text-diff creation
Reading snapshot files
Writing snapshot files
Other assertion exception message text
Our default snapshot serializers come with their own rules
There is currently no defined unique behavior about which kind of linebreaks we are using. The matter is complicated by the fact that snapshot files are supposed to be checked into the SCM and Git has its very own idea of dealing with line breaks among different seettings and operation systems.
Naturally, snapshot files are to be persisted with the linebreaks generated by the respective SnapshotSerializer
Naturally, snapshot files need to be read without losing any line break information (<- impossible due to GIT's beahvior)
Text diffs are always to be rendered with system line breaks. Line break changes are either highlighted separately at the beginning of the diff or ignored depending on diff settings
Likewise, all exception message text should be rendered with system line breaks
The text was updated successfully, but these errors were encountered:
We have several places where we deal with linebreaks:
There is currently no defined unique behavior about which kind of linebreaks we are using. The matter is complicated by the fact that snapshot files are supposed to be checked into the SCM and Git has its very own idea of dealing with line breaks among different seettings and operation systems.
SnapshotSerializer
The text was updated successfully, but these errors were encountered: