feat: JSON database #154
Draft
feat: JSON database #154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Autoparallel
force-pushed
the
feat/database-overhaul
branch
from
6d95dc6 to
d0bfe1e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP, aiming to:
learner): set up database versioning and migrations/scripts #134learner): add "tags" as a searchable component for paper in database #135learner): add "keywords" as searchable component in database #138learner): allow database query into abstract #97learner): allow forResourceas more general thanPaperin database #136I don't know if I will close these all at once, but I'm tempted to just go with a big sweeping overhaul, have a single breaking database change, then move on with something more extensible.