Stackedit: Do not insert stackedit_data to my documents

Created on 19 Feb 2018  路  12Comments  路  Source: benweet/stackedit

I've just tried StackEdit v5, it's a nice update over v4 but I was unpleasantly surprised that all of my Markdown documents just opened with StackEdit now contain something like this:

<!--stackedit_data:
erJoaXN0b4J5IjpbLTcwNjI2NTEyNl19
-->

Wouldn't there be a way to avoid this please?

Most helpful comment

I sort of understand technically but that unfortunately makes StackEdit unusable for me. Text editor should never be inserting arbitrary characters into my content.

All 12 comments

I'm afraid that's not possible. This footer is some extra data StackEdit needs to manage merges between different versions, collaborators discussions and file properties if any, sorry.

I sort of understand technically but that unfortunately makes StackEdit unusable for me. Text editor should never be inserting arbitrary characters into my content.

This is insane. What is the point of supporting the canonical Markdown syntax if you can basically only now use the .md files in StackEdit? This is such an amazing tool and then to utterly wreck it by adding this behaviour seems like madness to me.

Also a dealbreaker for me.

I'm sure a lot of people would be ok disabling those features in order to preserve their files clean. I certainly would.

It doesn't show in jekyll sites.

This is plain wrong, and forces me to stop using StackEdit. Why not use an external file (like swaps) or directory to track this?

This is ridiculous. Should at least have the option to toggle this off.

It will be cool if we just could choose to disable this, even if that means disabling some features.

@benweet
Would it be possible to at least include this in the somewhat standardized YAML metadata?
I'm imagining something like

---
title: My Document
stackedit_data: *data*
---

That way most markdown editors and workflows should ignore the information rather than try to render it 馃

@benweet
But what information does this metadata contain? Can it be used maliciously? Is it safe for the tag to remain in the source code of live websites?

@benweet
Would it be possible to at least include this in the somewhat standardized YAML metadata?
I'm imagining something like

---
title: My Document
stackedit_data: *data*
---

That way most markdown editors and workflows should ignore the information rather than try to render it 馃

This seems like a great solution. I wonder why it hasn't been considered

hello every guys,
In my case, I need to use it to publish my Docsify Pages, so I use the github workflow job to Find and remove the stackedit_data tags. Below is my workflow example, Watch carefully the replace job.

Replace:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Find and Replace
        uses: jacobtomlinson/gha-find-replace@master
        with:
          find: <!--[\s\S]*?-->
          replace: ""

Github Workflow For Docsify Pages Depoly

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dandv picture dandv  路  4Comments

tydel picture tydel  路  4Comments

gabrielacosta picture gabrielacosta  路  5Comments

alankis picture alankis  路  4Comments

joekaiser picture joekaiser  路  5Comments