3 kinds of changes had to be made to the unit tests only:
Use / as path separator - understood both on Windows and Unix
Use Environment.NewLine where appropriate instead of hard coding \r\n
Fix the unit tests to use the en-US culture.
The last point raises a question - should the razor engine allow its clients to provide a culture to be used when rendering? After all, the Asp.Net Core does allow to modify the culture through app config or for a single page. But here we do not seem to support it.
3 kinds of changes had to be made to the unit tests only:
/
as path separator - understood both on Windows and UnixEnvironment.NewLine
where appropriate instead of hard coding\r\n
en-US
culture.The last point raises a question - should the razor engine allow its clients to provide a culture to be used when rendering? After all, the Asp.Net Core does allow to modify the culture through app config or for a single page. But here we do not seem to support it.