You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Changes to snippets are immediately reverted a couple of seconds after the user stops typing #792
I noticed that new snippets created using v5.5.0 are using 3 backticks as the container format again, instead of 4 backticks. Was this an intentional change?
I've seen the issue occur a couple of times with snippets I created new in v5.5.0, but haven't figured out how to reproduce it. Is it possible that new snippets which are using the 3 backticks are still triggering the issue sometimes? Even with old snippets it doesn't happen every time. It's a bit random.
Thanks for checking. That confirms the likely cause.
The update path currently resolves fragments by contentId globally. With duplicate contents[].id values, an edit can hit the wrong fragment and then look like a revert after sync.
Activity
BryanWall commentedon May 13, 2026
I noticed that new snippets created using v5.5.0 are using 3 backticks as the container format again, instead of 4 backticks. Was this an intentional change?
I've seen the issue occur a couple of times with snippets I created new in v5.5.0, but haven't figured out how to reproduce it. Is it possible that new snippets which are using the 3 backticks are still triggering the issue sometimes? Even with old snippets it doesn't happen every time. It's a bit random.
antonreshetov commentedon May 14, 2026
Could you check whether the affected
.mdsnippet and nearby snippets have duplicatecontents[].idvalues in frontmatter?The
3-backtickfence itself does not look like the issue in v5.5.0. The serializer now chooses a longer fence when the content contains backticks.Example:
BryanWall commentedon May 14, 2026
Yes, several snippets in the same folder have the same contents block in the .md
The id: outside the contents block is different for each one, though.
I duplicated each snippet and deleted the original to fix the duplicate id: values.
antonreshetov commentedon May 16, 2026
Thanks for checking. That confirms the likely cause.
The update path currently resolves fragments by contentId globally. With duplicate contents[].id values, an edit can hit the wrong fragment and then look like a revert after sync.
fix(snippets): scope content mutations to snippets (#792) (#799)