Rose Robertson
Rose Robertson
If you test out markdown on a gist, markdown like this: ``` markdown **Test ** ``` (with trailing or leading whitespace) is not properly parsed. (examples here: https://gist.github.com/Rosey/3f848d77b46f7ab337a53211117acd87) This change...
Hello! Hopefully this is helpful. I noticed the regular expressions weren't being saved in a variable anywhere and were being created inside a `map` loop so decided to change that....
See failing test here: https://github.com/Rosey/markdown-draft-js/pull/107/commits/71b848bf9e7c1b3ed123643d2bd6095e9ecce5b0 Would only be an issue for people using `preserveNewlines: true` as by default stripping those newlines is correct markdown behaviour. However, we have a hack...
When I started on this project I was just kind of doing it for myself but I think it has enough people using it that I should be a bit...
Previous issue outlining the problem: https://github.com/Rosey/markdown-draft-js/issues/52 And current code for escaping basic markdown, with a comment on its limitations - https://github.com/Rosey/markdown-draft-js/blob/master/src/draft-to-markdown.js#L3
Just testing this on the spectrum.chat site: 1. start typing a message 2. Press cmd-b to make text bold 3. Continue typing Expected result: Text is bold from the time...
Sorry another one :) In a code block the enter key doesn't seem to work how I'd expect, when I hit enter nothing happens. In a blockquote it breaks you...