adding logic to handle windows line endings when content is pasted on… #63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… Windows machines.
OvidijusParsiunas
approved these changes
May 13, 2025
|
Thankyou for your contribution. This is now available in |
|
Thank you for accepting my Pull Request! Glad to have contributed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… Windows machines.
This commit closes issue #49. On Windows machines, when data with "\r\n" line endings was pasted, the active table cells would retain "\r" at the last cell in each row as shown below:
This commit handles Windows style line endings, fixing the issue as shown below:
