Can you try 'Dendron: Doctor' and see if that changes anything? I received this error message a number of times usually after creating notes outside of Dendron which lacked an id

Nope still get the error

Pity then someone more knowledgeable needs to take a look

@User what version of markdown links are you running?

0.6.17 even though the changelog says its version [0.8.0] – 2020-08-22

@User left some comments in the pull request. ui looks great. excited to play around with chakra 🙂 https://github.com/dendronhq/dendron/pull/351#pullrequestreview-536083935

Working on the feedback now 🙂

Thanks for the review!

lol @ the

data-FUCK

i was testing something in the DOM and wanted to spot it easily in the devtools 😅

lol, well, its effective

Quick clarity on the vault/hierarchy labeling: would you prefer that I simply made those fields look like root/notes/assets prefix/etc?

Or do you like them having their own section, just not the explicit

{index}

bit of the label?

If we're not gonna have

{index}

next to them, I think I might wanna just make them look like the other sections for now.

Hmm, lemme play around a lil considering some of the other feedback (namely, linking to the relevant dendron command pages)

can you see if there's anything in the server logs? also, whether upgrading to 0.17 has fixed the issues? https://www.loom.com/share/3d04cb1d6f904ac099d73e083e62ee2f

will check tommorow after work

🍿 preview.

love it. especially the subtle ui touches with the buttons! one small nitpick: the prettyref and copy assets should be toggled on by default 🙂

ooo, good catch, i had hard-coded otherwise by mistake. (they weren't in the initial stub + didn't look at the engine-server genDefaultConfig values after)

Fixed in my PR but i don't think i needed to since the

getConfigData

is just hardcoded right now anyway.

@User @User @User @User I just went through and added more detail on how multi-vault will work with version control: https://dendron.so/notes/45cfb9f2-46cf-4f67-a41e-834818fbd06e.html#initialization The gist is that each vault can be its own git repo. The layout of vaults inside a workspace is controlled from the Dendron configuration file (

dendron.yml

). You can initialize a workspace from a remote configuration file which will check out the configuration as well as all vaults associated with that config. The advantage of the above method is that you have a single source of truth to describe your workspace while still being able to keep each workspace as a separate git repo. Consider these plans as still works in progress so I welcome any feedback on this subject 🙂

@User Sadly the logs are empty and the schema graph atill does not work

so does that mean I can Have a Vault be part of a Software Project and Have the documentation for the project be in it. But still have the vault in my global workspace, for referencing the project in my private vault and my public vault.

hmm, do you mind sharing the output of both

dendron: configure

and

open workspace settings (json)

? is it only the schema graph that doesn't work or also the regular graph?

yep, absolutely 🙂

will do as soon as i am home from work and yes its only the schema graph that makes trouble.

so if i have two vaults, i will have 3 repos in total (+1 for workspace root), is that right? sounds reasonable to me

Did the check for

dendron.code-workspace

become case-sensitive at some point? I'm fairly sure that's the reason the extension stopped activating for me when I restarted VS Code 😅

The lookup binding worked but no suggestions were displayed and there was no interesting output in the Dendron outputs