It seems like my tests are failing because of the carriage returns on mac/Linux but works fine on Windows.
What's the correct way to fix this? Do I add a .Replace("`r",'') to all of the test strings and set my offset accordingly or can I do something to ensure the same line endings on all test platforms?

It seems like my tests are failing because of the carriage returns on mac/Linux but works fine on Windows.
What's the correct way to fix this? Do I add a .Replace("`r",'') to all of the test strings and set my offset accordingly or can I do something to ensure the same line endings on all test platforms?

One approach to this might be to avoid explicit multiline here-strings and construct the test strings like this instead:

$TestString = @(
    "line 1"
    "line 2"
    "line 3"
) -join [Environment]::NewLine

Good idea about using join. I ended up using a character that could easily be removed as a fake cursor, this also makes it easier to tell where the cursor is supposed to be when looking at the test.

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@MartinGC94 Please resolve merge conflicts.

I don't know how to resolve the merge conflict. Github has a "Resolve conflicts" button but there doesn't seem to be a way to save changes made there. I've tried creating empty space above my newly added tests to make room for the recently added test.

there doesn't seem to be a way to save changes made there

Press "Mark as resolved" after you edit.

Alternatively you could add the new code from main branch to your branch manually and push new commit.

🎉v7.2.0-preview.6 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes