Markdown Support on Description Field

Answered

Comments

4 comments

  • Official comment
    Avatar
    Rui Jiang

    Thanks for the suggestion (and the praise). Due to the way the description field is displayed in our various clients (VSCode, Atom) we have to keep it as short as possible. We'll keep it plain text for the time being.

  • Avatar
    Matt Davis

    I agree with the original poster - one of the most annoying things about cacher is having to name and create files for every snippet.  I've already named the snippet, why are you forcing me to name and create a file as well? The system should function more like Quiver IMO.  Cacher has a nicer UI but snippet creation / management makes more sense with Quiver.

  • Avatar
    Rui Jiang

    Hi Matt,

    Thanks for the feedback. I think there are 2 separate concerns here:

    1. Markdown should be supported in the description field - which I addressed above.

    2. Why snippet filenames are required - addressed below.

    Cacher follows the GitHub gist model of creating snippets, which means there could be multiple snippet files per snippet. A filename is needed in order to give our syntax highlighter hints as to how to color your code. We are considering workflow enhancements that make it easier to set defaults for these fields. Stay tuned.

  • Avatar
    Matt Davis

    Hey Rui - thanks for the response.  Files are not the only way to hint language highlighting - there could just be a dropdown to select which syntax highlighting you want for a given snippet.  If Cacher wants to create files behind the scenes as a means of storage that's fine, but it just sucks having to deal with the mental overhead of naming files during snippet creation / management.

    This is how Quiver handles snippets - i think this approach is much better.  For each sub-snippet there would just be a dropdown for selecting which type of highlighting you want. 

     

Please sign in to leave a comment.