Also, they don't have a comprehensive list of built-in commands in the docs... I only knew about

search.action.openNewEditor

because you mentioned it in the

tips

page @User

yeah, vscode api docs are interesting. they're both more and less comprehensive then you would want them to be. they do have good list of sample extensions though that I found really helpful: https://github.com/microsoft/vscode-extension-samples

encountered my fair share of dark corners of the api so if you run into anything, feel free to ping me or post it in our #748936364283920495 channel 😉

> they do have good list of sample extensions though that I found really helpful Yep, my extension is basically a modified helloworld sample haha

> encountered my fair share of dark corners of the api so if you run into anything, feel free to ping me or post it in our #748936364283920495 channel 😉 Will do, thanks 🙏🏼

if you're ever looking for more reasons to play around with vscode extensions, we have plenty of open issues 😇 https://github.com/dendronhq/dendron/issues

Yep, I would love to contribute to Dendron, except I have 0 experience or knowlege on TypeScript

Should I get familiar with it first before attempting anything else ?

I'll try to find a quick start guide or something, and get more familiar as it becomes necessary 🤔

if you're already familiar with javascript, typescript isn't that hard to pick up. there are guides like this that are aimed at javascript developers: https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html

imo, the hardest thing with typescript is configuring the project at the beginning. but we've actually set all that up for you so that (theoretically), you should be able to checkout the repo, run two scripts, and have everything ready to go https://www.dendron.so/notes/64f0e2d5-2c83-43df-9144-40f2c68935aa.html

if you're interested, happy to point you to some good starting tasks as well as walk you through the code base

Sounds good, thanks!

Yes I am interested, will first get a bit familiar with typescript and then ping you to help me pick an easy first issue to tackle

PS: I also 0 experience with TDD 😬

haha, all good. developer experience is something that can be taught but a passion for note-taking and structure is much harder to come by

all things being equal i prefer the latter over the former 😉

What better time to learn TS and TDD, I've been putting both off for quite some time haha. Will get a bit familiar with TS, clone the repo, snoop around a bit then start asking some questions 👀

> Loopback in days traversal is not what I found confusing, I'm talking about

august
     30
     31
september
     1
     2
     3

> If I'm in august and go to next sibling I expect to end up in september. But it sends me to august.30 Reposting in case this got lost in color theme discussion

it did! thanks for reposting. you're right, that's questionable behavior. will look into it!

>

> august
>      30
>      31
> september
>      1
>      2
>      3
>

> Reposting in case this got lost in color theme discussion @User it was a bug with how we were iterating through siblings. will be fixed today!

also - you've been killing it in terms of bug reports 🏆 🌱 🐛 🔨 = 🌲

👩‍🌾

@User If you have some code relating to an app, lets say, excel...How do you decide (no right answer) which heirarchy it should belong to? code.excel or excel.code context, my future self unfortunately may not decide correctly <>

hi @User , I guess it depends on what you are trying to do. Are you dealing with lots of code topics, excel being one, or lots of excel topics, code being one? In the former, I would select code.excel and in latter excel.code. However if there's not much content yet, I'd even just create a note called excel-code, and see where it evolves. The main use cases for me for the structure is to 1) find the content with the lookup, in that case even "excel-code" would work fine, 2) create taxonomy / mental model in my head for the things I care about, for this one has to have understand what one cares about. In case you think that both excel.code and code.excel are absolutely equal and they both should be created, you could also make one of them a "master note", and refer to it from the other note: https://www.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c.html#references-

@User I think this starts to be FAQ material 🙂

excel-code doesn't quite work for looking up "codeexcel" later note reference is a neat trick)

true, but since the autocomplete is incremental, by the time you've typed in excel, you probably already spot it - unless you have tens of notes related to excel

...(or code) - in which case you've probably already settled with a structure that you know