Yep, because it looks like that's how you'd capture the navigation events for analytics

got it. yep, it is. we wanted to give users more control with customizing their app which is why we released

nextjs-template

as its own repo. the challenge now is figuring out how to expose the right hooks/functionality so that it can be extended further in a way that allows for us to add new functionality to forks

one approach is

create-react-app

and exposing all customizations as a hook from the original project https://github.com/facebook/create-react-app

advanced customizations can be their own templates -- https://create-react-app.dev/docs/custom-templates/

now nothing stops you from just forking and making your own additions, its just that we won't be able to guarantee that subsequent changes to

nextjs-template

will be compatible with the fork otherwise

This command line call https://github.com/dendronhq/dendron/blob/master/test-workspace/scripts/dev.sh#L4 should be equivalent of running

api-server

locally isn't it?

Hi, can I post a call for participants in an interview study on open source projects here? If any mod wants more details via DM first, then I'm happy to oblige 🙂

Strange, I'm getting a javascript error in my system journal

js: Uncaught ReferenceError: refresh is not defined

I can't figure out where this is coming from

anyone got any pro tips on that

i think its jslint

definitely jslint

Extensions are fun to write! Interesting how I never felt quite so empowered by editing elisp in Emacs as I did changing an extension in VSCode 🤔

yeah, I know what you mean (for me it was vim extensions). other bonus is not having to write vimscript, 😅

Any good resources for getting started writing extensions? I’d like to write one to automate some interactions with Dendron.

VSCode's own getting started documents are pretty good: https://code.visualstudio.com/api/get-started/your-first-extension

Other than that, I look through their APIs or read Dendron's source code 😄

depending on the extend of automation, you can use dendron hooks to add custom logic to dendron https://wiki.dendron.so/notes/12551d19-04c2-4d26-ac1e-d23ff3181a9c.html

Thanks @User and @User. What I'm trying to build is an extension that will add a command to the Ctrl-Shift-P dialogue (and also have an assignable keystroke command) that will create a new note with the name

kb.note.{yyyyMMddhhmmss}

. Feels like hooks won't do this for me, unless there's a hook I'm not seeing.

The only part that seems a little tricky-ish is that when I create that note, I want it to be created from a schema, so integrating with Dendron is preferable.

If you want to, you could add it directly to Dendron, we are happy to accept contributions. I think you can already configure the prefix of a journal note, so all you would need is to add a configuration to let people customize the how the note name is generated for journal notes.

Thanks @User. I was working down that path too. It looks like in the

dendron.yml

file, I could change the

dateFormat

key to get the format I want. If I change the

name

key to

note

and the

dailyDomain

key to

kb

, would that be enough to subvert the daily journal feature to creating these notes? In other words, would that create the

kb.note.{yyyyMMdddhhmmss}

format?

The other approach I was considering was to augment the existing schema feature so a schema could have a key on it called

filename

where, in this case, I could set it to

kb.note.{yyyyMMddhhmmss}

(it could include the usual date strings). A new note created from that schema would default to that filename. Hypothetically, this would allow someone to create their own "special note" type without having to create an extension or modify the Dendron source. I prefer this change and would be happy to make it, but only if there's a reasonable chance it would get merged into the codebase. My worst-case scenario would be making a change that puts me on a fork that makes upgrades a challenge. Is a change like what I'm proposing in-line with the direction you want to take Dendron?

Actually, schemas may not work for that, given their focus on the hierarchy. Putting a key like that on templates might make more sense, but there isn't a great place to put something like that. I'll keep thinking about it. Any ideas would be great.

It could go on the schema if I added a key like

suffix

and could set that to

{yyyyMMddhhmmss}

. Then, any note created that conforms to the schema could have that added as a suffix. If I created a note called

kb.note

, then it would end up being the same as

kb.note.{yyyyMMddhhmmss}

. That feels a little hacky though. In the end, my goal is to create user-defined special notes.

This seems to work for me:

journal:
    dailyDomain: kb
    name: note
    dateFormat: yyyyMMddhhmmss

@User That works for me as well. I can do the same thing with the scratch note settings as well if I set the name to

kb.note

.

@kevins8 how's the UI work going? I'd like to help with the dendron-design-system package still when i find some time. Since you had just made the switch from Chakra to antd it slowed down my progress on helping there since i don't know that library well. Has the switch to antd been working out for the team?

On another topic of Monorepos, how's Lerna working for you? I've been doing some spikes on Monorepos and seen that the hot new kid on the block is Rush, and Lerna is kinda portrayed as inferior compared to it 🤔