AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Features

Horizontal rule markdown support

(#1385) Feature Under consideration markdown
by bizoReviewer originally by @bizojs on GitHub

Current problem

Currently there's no real way to naturally separate markdown content without workarounds such as using custom separator emotes

Proposed change

I would like to see Fluxer support parsing horizontal rules

Additional information

Some mockups of what this could visually look like: image image
  • 638262570-05571e62-6679-4222-b211-7307985f73aa.png

    638262570-05571e62-6679-4222-b211-7307985f73aa.png

    1110×521 | 40 kB

  • 638262695-1dc96452-82e5-4f2f-9b91-13c66572069a.png

    638262695-1dc96452-82e5-4f2f-9b91-13c66572069a.png

    1138×619 | 35 kB

2 comments

Sign in with Fluxer to comment and vote.
Comment by @Itsudemo
RexSystem 1 vote originally by @Itsudemo on GitHub 1 reply
This would be great for all sorts of uses, and the syntax presented in the markdownguide link seems about right. Save for one minor thing, that is: Fluxer prunes empty lines at the beginning and ends of messages. This would prevent the horizontal rule's use to begin or end a message, which is something I can see people wanting to do. Maybe foregoing the empty spaces as a requirement would help. With respect to the mockup though it looks borderline invisible and in practice would perhaps benefit from being brighter or thicker. I hope this ends up added in some form, either way!
Permalink
Comment by bizo
bizoReviewer 1 vote originally by @bizojs on GitHub OP
Good points, i don't think Fluxer prunes empty lines if they're part of the content, but yes this could be a concern if you were sending a horizontal rule as a separate message The colour in the mockup I agree is quite hard to see, it was more of a "mockup" from within Fluxer using inspect element, so I just stole the separator used to indicate a message was sent in a different day :P Appreciate the feedback regardless!
Permalink