Hmm, another question regarding publishing. Is it possible to get VS Code to remove the cached version of notes? Right now I'm making updates in the editor and trying the "site preview" but the previewed page doesn't include the changes.

I'm using GitJournal which obviously implies using Git for your vault(s). It seems to work generally fine (have been using it for a few days only), although it already crashed on me once. I create entries in a folder called

inbox

and then tindy things up when back in vscode.

I'd like to do a few tests with dummy files to quickly try out a few ideas related to using elastic search. Is there a standard / recommended way to do this?

--- Unrelated: I'd like to do a few tests with dummy files to quickly try out a few ideas related to using elastic search. Is there a standard / recommended way to do this?

One option to just experiment would be to create a new dendron workspace, add some notes and then export them using the elasticsearch pod.

Hey fudo, thanks. Yes I created a dedicated

tests

vault in my workspace, but I'd like to generate the notes automatically... I'm a coder so I can come up with something, but wondering the Dendron developers have some standard way to do this.

take a look at the dendron api-server this could help you, add notes per api calls https://github.com/dendronhq/dendron/tree/master/packages/api-server and the engine client could help you https://github.com/dendronhq/dendron/blob/master/packages/engine-server/src/engineClient.ts

That's promising. I guess my next question is: how do I instantiate a client now? Should I setup a development environment like it is described in the wiki? When I get that to run, how will the cloned repo's extension interact with the Dendron extension I already got installed? In short shouldn't this discussion move to the #748936364283920495 channel?

Sorry I hadn't read the

Development

note in the wiki, which already answered most of my questions 🙂

easiest way is to run the preview from the command line. the built-in preview currently caches and its a known issue that we're working on : https://wiki.dendron.so/notes/1399b5d2-28fb-4077-aa5f-c8edbe52bc5d.html#cli

Okay, thanks. I'll have a look there!

Ooh ... that was a feature I'd missed. Very cool. Actually the experience browsing localhost:8080 is actually what I'd like to see directly in the preview pane, only with the editor pane and the preview pane linked, so opening a new editor made the preview pane navigate to the same note, and following a link in the preview pane cause the corresponding note to open in the editor pane.

yep, its what we're internally calling the unified preview. its something we plan on shipping this year

Seems to work good with the CLI-approach. Thanks.

So I was able to start the

api-server

by cloning from github and launching the api-server on a terminal using

yarn start:integ

, but so far using the API has been mostly unsuccessful. I know it runs because it responds to, e.g.

http://localhost:3005/api/note/info

, but I could not yet figure out how to get some meaningful data from my workspace. For instance

http://localhost:3005/api/note/query?qs=journal

results in my REST client hanging indefinitely and an error in the terminal's console with the following message:

UnhandledPromiseRejectionWarning: Error: STORE is empty

Other than that, this is indeed interesting, as if I get to understand how to use the API to populate my test vault, I feel like I'll have achieved a big step forward in my little project. Also, I noticed a (mostly) empty nextjs project in the monorepo. Is it your intention to use the API with it?

Me I'm getting

Cannot GET /

on localhost:8080, what's wrong with my setup?

yeah, we're working on replacing a lot of the UI (eg. tree view) with web components from nextjs. the preview and publishing will also be unified as a nextjs app in the coming months

can you check if you have something already running on that port?

you'll need to initialize the server before you can call the apis. sorry, it's not well documented yet. will be adding this next week 😅

API_SERVER="localhost:3005"
WORKSPACE=""
curl --location --request GET "$WORKSPACE_URL/api/workspace/initialize" \
--header 'Content-Type: application/json' \
--data-raw '{
    "uri": "$WORKSPACE"
}'

Sorry, that's not entirely clear. What is

$WORSPACE_URL

here?

API_SERVER

does not seem to be used. And

$WORKSPACE

is the empty string in your example. Is it intentional or should it contain something? If yes, what? I tried

http://localhost:3005/api/workspace/initialize

with a json payload resembling what you give in the example with a few variations, without success. I'm always getting:

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>Error</title>
    </head>
    <body>
        <pre>Cannot GET /api/workspace/initialize</pre>
    </body>
</html>

$WORKSPACE_URL

is actually

$API_SERVER

and

$WORKSPACE

should be the full path to where you want the workspace to be initialized.

also,

it should be a POST 😄

yeah, totally mislead you @User . here's an example of initiating it locally for me

curl --location --request POST 'http://localhost:3005/api/workspace/initialize' \
--header 'Content-Type: application/json' \
--data-raw '{
    "uri": "/Users/kevinlin/Dendron",
    "config": {
        "vaults": ["/Users/kevinlin/Dendron/vault"]
    }
}'

Great, works like a charm now. Is it OK to use the same workspace as my "stable" dendron instance that works within VSCode "non-insiders"? I specified it just like Kevin above, only I just specified my

tests

vault under

config/vaults

. What is strange is that the notes query endpoint still returns docs from my normal ("vault") vault...

Hi folks, has math rendering in markdown preview enhanced stopped working? I read that vscode was including mathjax by default, has that caused a problem?

yep. you can use any vscode version. i'm not sure what you mean by the normal vault. could you add more detail?

math rendering should work fine unless its manually disabled in

dendron.yml

Yes sorry that was not very clear. It turns out I have two vaults in my workspace:

tests

and

vault

Even though I specified

tests

only under the

config

key for the initialize call, I still get documents from the

vault

vault. I hope that's clearer.

ah got it. the config key is actually an older arg, we currently just read from the

dendron.yml

from the

wsRoot

. the api is still in a state of iteration which is why it isn't formally documented yet 😅