i see what the issue is. doing a new build 🙂

@User just added a new build

checking! 😉

@User it worked! Thanks! Replied in the issue.

awesome! thanks for bringing it up. your other issues should be resolved with the release that's going out tomorrow 🙂

excellent 🙂

What's up with this message I'm getting when running the bootstrap?

lerna success - @dendronhq/plugin-core
pulling template...
fatal: refusing to merge unrelated histories
sync 0d5d532aecd8a5f2438dff1409a0678a1f9dcc04...

(doesn't stop me from doing what i wanna do right now, just.. seems like something i should care about)

@User you are seeing that because we just refactored the

dendron-template

repo and squashed a bunch of commits. we sync from that repo during bootstrap of

dendron

since we bundle those files with the extension. you can get rid of the error by running the following before you run bootstrap

rm -rf dendron/packages/plugin-core/build

Same error after running that & bootstrapping, unfortunately.

Totally unrelated, but I'm finding

antd

lackluster. It's got tons and tons of components, which is assumedly why you chose it, though my experience of learning via their docs and actually composing the components is a not-fun experience. Beyond that, I'm also finding that many quality-of-life bits that come from accessibility features (like being able to click on a label to focus a field) aren't present in

antd

. Frustrating. Have you looked at Chakra before? https://chakra-ui.com/ They just came out with v1 a few days ago, and I've been using the v1 RC at work for 3 months now. Solid stuff. I find the docs/API/composibility to be a lot more intuitive, plus the themeability is great (built in light & dark modes, color schemes, etc). From an aesthetics standpoint, I find Chakra looks WAY BETTER out of the box, too.

@User need to go out for a vet appointment but will checkout both the bootstrap and chakra stuff this afternoon

@User Everything ok?

routine checkup but also checking a lump that's growing

to round of the story, the lump turned out to be a benign tumor so all is good 🙂

@User took a look at the chakra stuff. it looks really solid. if you like it, i'm okay with giving it a try. did you want to use it for the dendron form-idable pull request?

I have some shortcut key suggestions that has been speeding my workflows and lessening the cognitive burden for both using dendron and context switching bwteen other apps.

Ctrl+R : Leader key for Schema funcitons

Ctrl+R, F2 : Schema rename

Ctrl+R, F5 : Schema reload.

Shift+Del : Delete node - this change opens up ctrl+alt+d, a high value left-handed shortcut, open for other commands. Some tasks are done with one hand on the mouse, and keys that can be pressed by one hand while on the home row should be saved for those tasks

@User i would like to use it for the form-idable stuff, indeed. i can swap chakra for antd in the same PR if you'd like, there's relatively minimal plumbing required to set it up. (should just a theme provider in the top-level app component i believe) happy to do the swap in its own PR beforehand too.

@User sounds good. ping me when you think its ready. excited to merge dendron's first enhanced UI feature 🤩

> dendron version

would be a good command -- or

> dendron info

... they could open a web UI that displays version, platform, etc ... maybe even a button to a web UI for dendron's logs.

Dendron: Report Bug / Feedback / etc

would also be a great command

Hi, so I wanted to have a

backlinks: []

attribute in the jekyll front matter of an export, and I thought that other people might too, so I thought I might as well submit a PR, but it turns out it's not as straightforward as I thought 😅 For one, I assumed that the

parent

and

children

props are generated during the export, but it seems that they're already a part of

DNodePropsV2

- so I guess I could add

backlinks

there, but that's a fairly drastic change - or I thought about adding them to `note2JekyllMdFile()`'s

jekyllProps

, but backlinks technically aren't a "jekyll prop" either (they're not specific to jekyll is my point) - any guidance? (Also, I wasn't able to find where the Backlinks panel resides in the codebase so far, which might answer some questions too)

(Oh and, I am kind of assuming that it's something worth sending a PR for - I would've sent a Feature Request / Issue first, but I wanted to try whether I am even able to make the contribution at all)

@User I found this and I thought it might be useful for the recent feature request I had https://github.com/andymatuschak/note-link-janitor

Interestingly enough, it seems that Andy's notes could almost be backed by Dendron... :)

> > dendron version would be a good command -- or > dendron info ... they could open a web UI that displays version, platform, etc ... maybe even a button to a web UI for dendron's logs. @User think that's a great idea. @User is going to be working on a github issues pod so that you can post a note as a github issue which would make this even easier. feel free to submit an issue for it 🙂

> Hi, so I wanted to have a backlinks: [] @User every note has a

links

section that tracks links it has. in order to get backlinks, we currently iterate through all note metadata and find notes that point to the current note: https://github.com/dendronhq/dendron/blob/master/packages/engine-server/src/drivers/file/storev2.ts#L527:L527