b513b94026
when created from app or cli. Moving db-worker to node changed the js/process exist check in db-ident ns. Brought back env var for straightforward fix. I checked other process checks and this was the only one affected this way. Also remove double testing for graph-parser as it hasn't provided any benefit and yet another place where we kept juggling this env var
1.8 KiB
Description
This library parses a file graph directory and returns it as a datascript database connection. This library mainly exists to convert file graphs to DB graphs. 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.graph-parser. This library
provides two main namespaces, logseq.graph-parser.exporter and
logseq.graph-parser.extract.
Usage
See nbb-logseq example scripts 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 frontend 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
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.