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 }}
This repository has been archived by the owner on Oct 7, 2022. It is now read-only.
With the yaml feature the db file looks like this:
---
Key: "---\nasd: []\nfoo: \n bar: []\n baz: 0"
This isn't really human readable/editable because of the newlines and whitespace sensitivity in the string.
Was it really intended to store it like that (value as escaped string)?
That seems to be a limitation of the yaml library? All we do is write whatever encode gives us back. If you have any backward compatible ideas I'm happy to merge them!
RON sounds like a good addition. I would support adding it as a backend, maybe you can open a seperate issue/PR for it?
With the yaml feature the db file looks like this:
This isn't really human readable/editable because of the newlines and whitespace sensitivity in the string.
Was it really intended to store it like that (value as escaped string)?
Btw, what do you think of RON as an option?
The text was updated successfully, but these errors were encountered: