@User this is what it looks like

Yeah, I got it once I discovered that I named the clause in the .yml 'def' instead of 'dev'...

Just was checking it out. That cryptoscape library seems interesting, never saw that before.

Yeah, this has been a new look into the graphing space for me - it's been pretty interesting so far!

I made another PR to update the dendron-design-system RFC, w/ ant design discussion (after switching from Chakra UI). Take a look when you have time @User @User @User https://github.com/dendronhq/dendron-site/pull/102

approved 🙂

in terms of themes, we currently update the theme manually using the generated less files: https://wiki.dendron.so/notes/1698aef0-efd4-4c92-a3b0-5ca702b228a3.html#updating-the-theme the plan was to have a custom folder (eg. ~/.dendron/themes/) for peopel to generate their own themes that they can set. dynamic would definitely better though. for dynamically setting the ant theme, i was looking into this: https://medium.com/@mzohaib.qc/ant-design-live-theme-588233ea2bbc regardless of if we go with dynamic or static theme setting in the plugin, it would be great to have the dynamic theming in the design system 🙂

custom folder (eg. ~/.dendron/themes/)

I would think this approach should work fine w/ the next.js webpack.config.js approach. It would probably require a restart next server / or redeploy but I think that would be fine/ expected. If the user wants to have those theme settings persist indefinitely than they new theme files would need to go to source control wouldn't they ? - https://medium.com/@mzohaib.qc/ant-design-live-theme-588233ea2bbc Just checked that out and they dynamic theme settings are being saved in local storage, so the updated theme would only be available on the same browser/ non-inognito mode. But I'd imagine the users updating their theme would want those to persist everywhere?

@User @User Here the mentioned repo that I mentioned during office-hours: https://github.com/flammehawk/dendron-schemas And yes I need to clean up certain bits a bit, to make it work you need to use pnpm, since that's a personal preference from me.

heads up that with the latest release, we now have a

docs

section in the weekly release to go over documentation updates. a lot of it is developer related! you can check it out here -> https://wiki.dendron.so/notes/00e6f3d8-4243-42c7-8e4f-a074a1bd0ffb.html#docs

Hi, in the setup documentation I found: To start an instance of the Dendron with the Debugger, Run Extension (plugin-core) from the debug panel in vscode. But I can only find these below options. Which one of the following is the correct one to start debugging

if you are running it locally,

Run Extension:Local (plugin-core)

would be the one.

How to run a newly created builtIn export pod with id, say "dendron.somepod" inside somepod.ts file ? (consider that the pod is returned from getAllExportPods() method of pod-core/src/index.ts as well)

>Dendron: Export Pod

command

you should be able to pick the new pod from there

I tried this command, seems like there's something missing, since the newly created dendron.somepod was not coming in drop-down

Even if I remove some of the pods from return of index file.. i was still able to see those pod in drop-down after export-pod

make sure you are compiling the code -->

bootstrap/scripts/watch.sh

should be running in the background

Hey folks, if you're interested in dedicated #748936364283920495 notifications, head on over to #849368750951104583 and grab the role. Let me know if you have issues doing so.

quick question are their some testing Frameworks That can be recommended?

we use jest for everything except the plugin. for that, we use mocha (because its well integrated with vscode)

kk

@User is there a way to limit dendron cli's query to do an exact match (specifically

engine.queryNotesSync

to do an exact match)? I'm passing in a query to it so that when the doctor command is scoped to the current active document, it only runs on that note. I am passing the fname of the active document to the doctor cli command as

query

but I think the fuzzy matcher is grabbing more.

getNoteByFname and pass it note and vault

ah, okay. I wanted to see if I can do it without directly passing it. will go that way.

Hey, can we add any additional npm package which we may require in dendron code?

yep. we should have a section in the docs about adding new packages

@User Took me a while but I finally had a chance to look at the json schema repo https://github.com/flammehawk/dendron-schemas/tree/main/components/dendron-json-schemas this is a great start! i think we can work on incorporating it initially as a CLI to validate existing schemas, first as a standalone and then part of the dendron cli some potential utilities

sh
dendron schema validate $schema
dendron schema generate --from $jsonSchema

xD I was more going into the direction of providing a build tool that would bundle the Json Schemas and copy them to where you want them, in the end the plugin would just link them under to provide validation, but yes it can be used as a cli as well.

json
{
  "contributes": {
    "{SchemaFile}": "*.schema.yaml"
  }
}

@User heads up that the RFC for the dendron seed bank is now published -> https://wiki.dendron.so/notes/4039fc46-06b2-4f83-b817-fc490bafbcb3.html this is essentially npm for knowledge - its our effort to modularize information to make it more accessible and composable for human consumption. this is still an early draft. all discussion welcome here -> https://github.com/dendronhq/dendron/discussions/802 🙏 @User @User @User @User