When running the test suite on my Windows machine, the paragraph test fails. The expected JSON contains the \r carriage return character. Presumably, this test passes on Linux machines.
The reason this issue occurs is somewhat complex. In order to check for dropdowns, the program will seemingly only separate lines of text that are separated by two new lines (\r?\n\r?\n) rather than one (\r?\n). Consequently, lines of text separated by two new lines will be read as two inputs, and their carriage feed and new line characters will be removed. Meanwhile, lines of text separated by one new line will be read as one input, with carriage feed and new line characters remaining within the text.
I believe I have a PR that will address this issue, as well as unify the way new line characters are considered when the action converts the issue body text to JSON.
Operating System: Windows
Node Version: v21.7.1
When running the test suite on my Windows machine, the paragraph test fails. The expected JSON contains the \r carriage return character. Presumably, this test passes on Linux machines.
The reason this issue occurs is somewhat complex. In order to check for dropdowns, the program will seemingly only separate lines of text that are separated by two new lines (\r?\n\r?\n) rather than one (\r?\n). Consequently, lines of text separated by two new lines will be read as two inputs, and their carriage feed and new line characters will be removed. Meanwhile, lines of text separated by one new line will be read as one input, with carriage feed and new line characters remaining within the text.
I believe I have a PR that will address this issue, as well as unify the way new line characters are considered when the action converts the issue body text to JSON.
Operating System: Windows
Node Version: v21.7.1