Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid json format #52

Closed
nothub opened this issue Oct 28, 2021 · 1 comment
Closed

invalid json format #52

nothub opened this issue Oct 28, 2021 · 1 comment

Comments

@nothub
Copy link

nothub commented Oct 28, 2021

A json file I generated with jsondb has multiple top-level values and thus (afaik) is not a valid json document.
Is there a way to configure jsondb to create entries under a single top-level value?

Example:

{"schemaVersion":"1.0"}
{"id":"foo","nickname":"a","onlineTimeSeconds":0,"lastSeenMillis":0,"ignoreAfk":false,"movedToAfk":0}
{"id":"bar","nickname":"b","onlineTimeSeconds":0,"lastSeenMillis":0,"ignoreAfk":false,"movedToAfk":0}
{"id":"baz","nickname":"c","onlineTimeSeconds":0,"lastSeenMillis":0,"ignoreAfk":false,"movedToAfk":0}
@FarooqKhan
Copy link
Collaborator

FarooqKhan commented Nov 5, 2021

JsonDB is desiged this way, each file is equivalent to a collection, and each entry is equivalent to one document. There is no way to make the entire file a valid JSON document

@nothub nothub closed this as completed Nov 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants