I don't see anything about note commands on the wiki page here https://wiki.dendron.so/notes/23a1b942-99af-45c8-8116-4f4bb7dccd21/ But they seem to exist in code. Maybe they haven't been added to the docs? https://github.com/dendronhq/dendron/blob/master/packages/dendron-cli/src/commands/notes.ts

It's here: https://wiki.dendron.so/notes/xI97d5GKk7qU6EwstIAXe/

Ah, okay, it's in a different section, somehow I couldn't find it via the search, but that's old news! 🙂

Just curious. What kind of hooks are you thinking about implementing? Would be nice to add it to our awesome-list if you wish to share it with the community 🙂

Yeah, will be open source. I want to track all my contacts in dendron (really in markdown + yaml), and then keep my address book in sync. So that's one piece. I also want to be able to see my notes online, at the very least, today's journal note. Then I want to be able to see other notes. Then I want to be able to check off checkboxes in notes, and after that, make other edits.

I have a feeling that the issue with lookup not applying traits to lookups will stop me being able to create new journal notes from the cli, but maybe that'll be fixed soon! 🤞

I see there's an API server, is that something that's considered "private" in the sense that it's not meant for external consumption?

@User just started a discussion on standardizing feature documentation here: https://github.com/dendronhq/dendron/discussions/2298 Welcome to join and add any thoughts.

Yes, the API server is for internal use. an express server that runs locally when you use Dendron in VSCode.

I've dug into the code a little, and was looking a bit at the architecture docs, but I couldn't see any docs for the API shape, so I figured it's not meant to be used by third party apps, maybe isn't strictly versioned, etc.

Yes it's not specced out to be used generally 😅

Is there any kind of debugging possible on the cli? I get no output at all for all my queries...

I tried

DEBUG='*' dendron ...

but that doesn't seem to work.

Also, adding

--version

does produce output, as does

--help

, but neither one produces an error despite being added to the end of a different command...

Ah, I see the issue, I typed

notes

instead of

note

, will file a bug.

publishing optimizations

you want to set the log level

LOG_LEVEL=debug

before running the CLI

Happy Friday @User! We've had a lot of interest from folks who would like to contribute to Dendron's codebase but aren't sure where to get started. To help, we'll be picking out weekly

good first tasks

that will help introduce you to the code while also making a noticeable contribution to an existing feature. Each of these tasks should take no longer than an hour to complete end to end. If you choose to take one on, a member of the Dendron team will help walk you through the process -- just leave a comment on the issue. Here are this week's tasks: - [#2238: Move Header Should Have Current Hierarchy Prefilled](https://github.com/dendronhq/dendron/issues/2238) - [#2186: Prompt "are you sure?" before deleting .next directory with publish init command](https://github.com/dendronhq/dendron/issues/2186) - [#2300: CLI does not report invalid commands](https://github.com/dendronhq/dendron/issues/2300) For help getting set up, see our [contributing docs](https://wiki.dendron.so/notes/81da87be-2d4e-47b5-a1d6-c0d647e1ab00/).

Several vscode extension optimization tips https://jason-williams.co.uk/speeding-up-vscode-extensions-in-2022

@User since we've been talking about github caching and whatnot, it inspired me to optimize the action for dendron's pipeline: https://github.com/dendronhq/dendron/pull/2308 33% improvements in build times, with more coming once we fix up some flaky test 🙂

Broskis has anyone heard if a feature of changing note hierarchy through the graph view is on any dev's mind?

good first tasks

Hey folks, I need some feedback. I'm trying to migrate some parts of MDUtilsV4 to MDUtilsV5. One thing I'm wondering about though is how to do the proc plugin options (like

proc.use(wikilinks, opts)

). With V4 these options were both attached to the plugins, and also added to the proc data (because there are some places where plugins other than the intended one need access to the opt). I'm wondering if that's the best way to handle this though. We could instead do: - All opts should be in proc data. Don't pass them into the plugins, have the plugins get it from proc data. - All opts should be passed to plugins only, never to data. If more than one plugin is interested in those opts, we can pass the opts to them as well. I'm actually leaning a bit towards the former option because it's much more flexible. It does make these plugins even more tightly coupled with Dendron, e.g. someone couldn't grab these plugins without the rest of Dendron's proc. I think that's an okay tradeoff at the moment, and we can always come back and refactor this code if we want to make the plugins available outside of Dendron.

procutils configuration

Why does MDUtilsV5 add

dendronPub

plugin even when the destination is not HTML or flavor set to publishing?

not supported right now but feel free to submit a feature request 🙂

Hey folks - wrote a small snippet on a gotcha when testing async callbacks with jest/mocha: https://docs.dendron.so/notes/FfyL5dSzFwX1iseI56oYy/#testing-the-invocation-of-a-callback

Hey folks: I have an RFC for "Self Contained Vaults" to announce! This RFC will combine the concepts of "Dendron workspaces" and "vaults", and make it easier to share and reuse vaults. Any feedback or suggestions are welcome: RFC: https://docs.dendron.so/notes/aOOBYTowLEKJDEtLWFiHb/ Discussion: https://github.com/dendronhq/dendron/discussions/2349

@User @User wrote a guide on troubleshooting build issues in case anyone encounters build errors: https://github.com/dendronhq/dendron-docs/commit/861cdfd79817cbf361c897b86c4c9baaa75bc17e