ability to at-mention users in bucket comments

[jlopker]

No description provided.

[jlopker]

@chime-mu

a problem that I'm not sure how to fix.. I'm using #{root_url} for the user links in the email but it's interpolating that to mean localhost:3000 which is the backend root. when i use #{root_url} in the emails templates, it interpolates correctly to localhost:9000. do you know anything about why this is happening?

[chime-mu]

@jlopker There's <br> and a </a> in the comment, so still a mixture of HTML and markdown

This is from parameters in the POST http://localhost:3000/api/v1/comments

body: Test I can do basic markdown _italic_ <br><br>*another italic*<br><br>**bold** </a><br>

[chime-mu]

@jlopker When I use a header all text become header sized:

body: # Header<br><br>Normal text<br><br>Another line<br>

[jlopker]

@chime-mu Ok this is officially the most annoying feature ever. But! I think I may gotten it..

The comment field is a contenteditable div rather than a textarea which is why we were getting all that html markup. From my current thinking, it needs to be contenteditable because we need to transform the user name into something that carries information about the userid. And because we can't hide that kind of information in textareas, I thought we needed a contenteditable div.

I'm now using jQuery to strip out the html and turn the inputted comment into text. It's not an elegant solution though :(. I tested it with all the kinds of markup I could think of and it seems to be working. Let me know how it goes for you! Thanks.

[chime-mu]

@jlopker Now linebreaks are completely gone.

This is expected output (taken from prod):

This is what happens in the @-mention branch:

For the header problem, this is expected output:

This is what happens in the @-mention branch: