9fff912f1e
- Split out reusable fns to their own ns - Created graph now initializes all the same data as in the app - Had to make a copy of block-with-timestamps for nbb compatibility and started using it in a couple places that are easy to QA |
||
|---|---|---|
| .. | ||
| .carve | ||
| script | ||
| src/logseq | ||
| test/logseq/db/sqlite | ||
| README.md | ||
| bb.edn | ||
| deps.edn | ||
| nbb.edn | ||
| package.json | ||
| yarn.lock | ||
README.md
Description
This library provides a minimal API for using a datascript or SQLite database from the Logseq app and the CLI. This library is compatible with ClojureScript and with nbb-logseq to respectively provide frontend and commandline functionality.
API
This library is under the parent namespace logseq.db. This library provides
three main namespaces, logseq.db, logseq.db.rules and logseq.db.sqlite.db.
Usage
See the frontend for example usage.
Dev
This follows the practices that the Logseq frontend follows. Most of the same linters are used, with configurations that are specific to this library. See this library's CI file for linting examples.
Setup
To run linters and tests, you'll want to install yarn dependencies once:
yarn install
This step is not needed if you're just running the application.
Testing
Testing is done with nbb-logseq and nbb-test-runner. Some basic usage:
# Run all tests
$ yarn test
# List available options
$ yarn test -H
# Run tests with :focus metadata flag
$ yarn test -i focus
Datalog linting
Datalog rules for the client are linted through a script that also uses the datalog-parser. To run this linter:
bb lint:rules
Managing dependencies
The package.json dependencies are just for testing and should be updated if there is new behavior to test.
The deps.edn dependencies are used by both ClojureScript and nbb-logseq. Their versions should be backwards compatible with each other with priority given to the frontend. No new dependency should be introduced to this library without an understanding of the tradeoffs of adding this to nbb-logseq.