![]() ![]() The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li. Typing will let you tag a tool, and typing # will allow you to tag a topic. We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.Īlso we used React-Mentions for tagging tools and topics in the decisions. Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need. ![]() We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend. For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |