i think it should. if you change it, do any tests fail? 😅

what's a

nativeview

? Curious if it lets you reproduce the vscode look-and-feel? https://github.com/dendronhq/dendron/blob/dad85f6e1964b5cf21bc0a1007c229c504e17eb5/packages/common-all/src/constants/views.ts#L44

native views are built in vscode views (so regular tree view or customeditor view vs a webview)

more integrated but more limited. eg. see api for vscode treeview: https://code.visualstudio.com/api/extension-guides/tree-view

@User heads up that I compiled a list of frontend projects in this github discussion - https://github.com/dendronhq/dendron/discussions/2491 this came from a conversation I had with @User about Dendron's current frontend backlog if anyone is interested in picking up some frontend work, please post in the gh discussion for more details 🌱

Hey, why is there a

DendronDevConfig

in

src/types/workspace.ts

but also one at

src/types/configs/dev/dev.ts

? Is the former legacy or deprecated?

the one in

workspace.ts

is what's currently in use. we planned to do a migration so

dev.ts

was written during the first phase but there's not much point. I will have to clean up the types at some point but until then, use the one in

workspace.ts

Woah fun api, glad I asked

Huh wow, never knew about this syntax:

ts
let vaults;
({ vaults } = await this.handleRemoteRepo(opts));

yeah, its convenient! i quite like modern js syntax around variable assignment/destructuring

destructuring was beautiful when it was added to JS, especially when I was using React

I'm having trouble finding the message typedef to simulate an init call (from browser mode).

init

is enumerated in

DMessageEnum

there's no

init

action in

ideSlice

or match in

useVSCodeMessage

handlers

I see [[Lifecycle|dendron://dendron.docs/dendron-engine.ref.engine#lifecycle]] and it looks like

init

is not exposed anywhere but in

setupEngine

? https://github.com/dendronhq/dendron/blob/8ac57f1fd50b4fc9f62f9aa0ff8a7093bcfd179f/packages/engine-server/src/enginev2.ts#L260

no rush but cc @User - @User mentioned you were touching schemas a bit ago

just an ack that i saw this - in meeting now but will be free in ~45min for a response

no worries, sorry for not surfacing this sooner 😖

you can use something like the following to do the sync

js
id = "9eae08fb-5e3f-4a7e-a989-3f206825d490";
window.postMessage({
  type: "onDidChangeActiveTextEditor",
  data: { note: { id }, sync: true },
  source: "vscode",
});

notice the main diff from the example is

sync: true

, this tells the view to do a full sync with the engine instead of displaying the passed in note

for v2 pods, are we planning to support plugin style or are we limiting it to core? I've got a v1 confluence export pod kinda working, and trying to figure out what I should be doing to support v2

we are absolutely going to support plugins. we're migrating things over slowly to make sure theres a stable api to develop against. if you have any feedback from developing the v1 pod, would love to hear it 🙂

Biggest blocker/road bump I'm hitting right now is that while Confluence will accept HTML, it's somewhat picky (e.g., it won't allow links to no where). So I'm having to kinda tune the rehype parser to fake things out. Another "issue" (along those same lines) is that Confluence has its own macros for certain things like code fences. While it will respect the default remark output, I'm currently trying to figure out if I can short-circuit that in some way so I don't have to decompose that output with unist.

Is there some function I can use to get a note by ID? I see how to get it by path and fname, but not ID.

@User should the note hierarchy input for the schema validator have autocomplete? I imagine the lookup command palette autocomplete is straightforward to access?

engine.notes[id]

is the way to go for that

are schema templates already validated at any point? should they be?

I'd like to watch

common-all

and my dendron-plugin-view at the same time. When I run

./bootstrap/scripts/watch.sh

and

dendron-plugin-views/$ yarn start

, though, I get this error:

../common-all/lib/dnode.js
Module not found: Can't resolve 'console' in 'dendron/packages/common-all/lib'

you can repro by checking out

enhance/schema-page

and running

packages/dendron-plugin-views/$ env REACT_APP_VIEW_NAME=DendronSchemaPageView yarn start

with

./bootstrap/scripts/watch.sh

https://github.com/dendronhq/dendron/blob/master/packages/plugin-core/src/commands/NoteLookupCommand.ts#L167:L167 for autocomplete

what do you mean by validating schema templates? in the sense that they are a valid markdown file?

it looks like you have the following change in common-all +import { debug } from "console"