Newline behavior in GitLab is weird
GitLab's translation of what a user wrote into what the reader sees regarding newlines is unintuitive and leads to bad formatting. A newline in this comment box means nothing in the final output. One has to dig through documentation to find that one needs to add two spaces at the end of a line to get a newline in the final output. Why? None of my GitLab-using friends or colleagues expect this, because it is not standard behavior, and we end up with unreadable bug reports. Now that many Linux projects are moving away from Bugzilla to GitLab I see the same mess in the comments.
Why not make this editor WYSIWYG regarding newlines? At least having the option of doing that would be great.
Example:
Hello
There is a bug in version 1.
Look at this link: (foo)[http://bar.com]
And look at that link: (bar)[http://foo.com]
By the way, I don't know how to add links in a comment, there's no "Add link" button.
If I select bar, I get baz.
If on the other hand I select foo, I get qux: abc 123
Lorem ipsum, see screenshots. The user types this text, hits enter, and attaches an image, expecting the image to appear under it, as happens in all other platforms they use.
An arcade video game created by Tomohiro Nishikado and released in 1978:
The player defeats an alien, and earns points, by shooting it with the laser cannon:
Here is what I wrote:
The formatting in the "Write" field is not great, but it's completely readable, unlike the final result.