trial and error

hi @User , there's a schema-based use-case i need some help with. my notes hierarchy is this

tech
tech.readings
tech.readings.papers
tech.readings.books
tech.readings.articles

now im trying to do two things: 1. create a schema for

readings

parent which can be used for any parent (other than

tech

) e.g.

personal.readings.books

etc 2. apply different templates to each child i.e.

papers

,

books

and

articles

i currently have a file called

tech.schema.yml

that looks like this:

version: 1
schemas:
- id: tech
  desc: all notes in tech hierarchy 
  parent: root
  namespace: true
  children:
    - articles
    - books
    - papers

- id: articles
  desc: notes based on articles i've read

- id: books
  desc: notes based on books i've read

- id: papers
  desc: notes based on whitepapers i've read
  template: 
    id: readings.papers.template
    type: note

but when i create a note using

tech.readings.papers.foo

, the template

readings.papers.template

is not applied to the note. am i doing something wrong here?

did you ran Reload Index @User

yep, bunch of times, just to be sure 😄

hmm, trying to re-create it but seems to be working on my end https://www.loom.com/share/d4b51424d8f94d1db0627b7d9e29d63b

can you do a

Developer: Reload Workspace

, create

tech.foo.papers

and then send me the output of

Dendron: Open Log

?

ah! it was a miss on my part(as expected). instead of doing

tech.baz.papers

(like you did), i was trying

tech.papers.baz

which does not really match the glob pattern of the schema. i changed the schema to this:

version: 1
schemas:
- id: tech
  desc: all notes in tech hierarchy 
  parent: root
  children:
    - readings

- id: readings
  desc: technical readings 
  children:
    - articles
    - books
    - papers

- id: articles
  desc: notes based on articles i've read

- id: books
  desc: notes based on books i've read

- id: papers
  desc: notes based on whitepapers i've read
  namespace: true
  template: 
    id: readings.papers.template
    type: note

and create a note using

tech.readings.papers.baz

which applied the template correctly

👍

also, nice going adopting version 1 schemas 🙂

i'm still wrapping my head around it to be honest but i can definitely how're they're super useful. thanks for helping out!

yeah, it's probably the most complicated topic in dendron at the moment but working on simplifying it (and everything else) over the next couple of weeks

cool! that'd be awesome. i think schemas can support quite complex scenarios(im trying to squeeze a few of mine with current functionality). looking forward to all the changes in future!

yeah, definitely. with imports, it will be a lot easier to make re-usable schemas. will be awesome once people can start sharing and building off each others schemas

its a little messy but i've been fleshing out my schema for programming languages

definitely! once enough templates and real examples are available, it'll be much easier to onboard (and re-use) the schemas

that's the plan 🙂

kevin: Any way to customize the daily.journal command? My journals are made without dashes...

yep. daily journal notes use the same configuration as the journal command

awesome thx

> @User i think this is the same issue that we saw earlier. can you tell me what version of dendron markdown preview enhanced you have? if you un-install the extension and re-install or upgrade, it should make it go away @User Here is another issue, and no, reinstalling 0.5.17 didn't do the trick: enhanced.openPreviewToTheSide' not found Please help me out here...

kevin: Is there anyway to put all the daily.journal files in a folder so I don't have 365 of them in my main tree?

@User I would also like to know if this is possible or not

@User > @User Here is another issue, and no, reinstalling 0.5.17 didn't do the trick: enhanced.openPreviewToTheSide' not found Please help me out here... @User that was my bad. a regression in the 0.8.0 version. if you upgrade to 0.8.4 (just pushed), the issue should be fixed!

@User @User the current model for dendron is to have all files in a single folder (eg. my main dendron vault has around 6000 notes). you'll be able to partition your notes into multiple folders when support for multi-root workspaces is shipped (https://github.com/dendronhq/dendron/issues/9). meanwhile, if you really want to separate your notes, I would recommend initializing a separate workspace (eg.

Dendron-journals

) though that would mean losing the ability to create links between your journal notes and your other notes. is there a specific reason you don't want your journals in the main tree?

I guess I just like getting to my files using the tree. But I can see once I get a lot of notes then using the lookup would be better. Its fine

got it! would something like this work for your use case? https://github.com/dendronhq/dendron/issues/125

yes!!

that would work great

thanks man