[BUG][DOCS GENERATOR] Newlines aren't properly trimmed

[ViMaSter]

Describe the bug

Generated Markdown files sometimes contain superfluous line-breaks.
Example:

• correct amount
• incorrect amount

This does not impact how the files are rendered (notice both entries having the same amount of newlines in the preview versus the source code linked above), as Markdown consolidates newlines into one.

Steps To Reproduce

• Unclear. I suppose this has to do with how the GitHub Actions runner handles newlines (\r, \n \r\n) and therefore isn't reproducible on Windows for me at the moment.

Expected behavior

• No matter which OS the documentation generator is run on, the correct number of line breaks is added to the generated markdown files

[girijakar]

Hi @ViMaSter
I had gone through all the markdown files in the docs folder. Couldn't find any lines having incorrect amount of space as you have described :)

[ViMaSter]

Hey! Thanks for looking into it; and welcome! Good to know the current docs are fine so far.

Which OS are you running? 093810a definitely allows the issue to be reproduced if you're running the docs_generator on anything Unix-based.
If you're managing to reproduce that, stepping through https://github.com/Studio-Lovelies/GG-JointJustice-Unity/blob/develop/docs_generator/Scanner.cs#L117 and checking if anything surrounding methodInfo.Summary contains superfluous \n or \r, could probably shine some light on where these line-breaks come from. After that, it's only a matter of trimming them; either inside the source it's parsing or during doc-generation (which I think is the safer approach).

Definitely feel free to open a PR, if you're managing to reproduce and resolve the issue!

[girijakar]

I am running Windows.

[ViMaSter]

Just checked it out, the issue is actually reproducible on Windows as well with git config core.autocrlf set to input, but probably just limited to the line endings present inside 093810a which isn't merged into develop yet.
If you want to look at it further and manage to resolve it for that commit, feel free to create a PR with those changes targeting develop!