[Proposal] Persisting the state in the markdown itself

[MohamedBassem]

Hi, I noticed that the state is currently being persisted in local storage. I found this a bit confusing specially because my moves don't get synced to my other devices. So I'm wondering, have you considered persisting the state in the markdown block itself?

Basically, everytime the user does a move, update the markdown block with the new PGN/FEN. I've implemented this in my fork (https://github.com/MohamedBassem/Chesser) and I'm happy to send a pull request if you think that this is a better approach than using local storage.

Here's a video with the feature in action

Chesser.mov

[Bencbabcock]

This is awesome! how would I go about adding this to my vault?

[liamcain]

I had originally implemented the state saving feature by persisting to the markdown itself, but afaik, it requires rebuilding the game state each time. This ran into some issues with the chessboard not properly handling undo/redo, some issues with the arrow shapes not being serialized correctly, and some other issues that I can't recall right now. I had some future plans to just switch to adding a "save" button that would dump the localStorage data to the markdown manually, but I never got around to adding that feature.

I'm open to accepting a PR!