https://www.dendron.so/ logo
Join Discord
Powered by
# questions
  • k
    @User made a short todo case study. let me know if this is helpful: https://www.dendron.so/notes/593206ea-5658-4874-bafd-18a138870f91.html
  • r
    thanks Kevin that helps
  • r
    Can anybody recommend a good markdown cheatsheet?
  • k
  • r
    thx man
  • b
    @kevins8 spot on! Thank you for this video. I will try this first thing tomorrow . 👍
  • r
    uhhh I am having some issues with trying to get the schema working. (I'm sure it's me). I have a schema file name pro.schema.yml and I have this in it. - id: pro desc: projects parent: root children: - work - id: work namespace: true children: - python - id: python namespace: true desc: python projects 2020
  • r
    I am trying to be able to type pro.work.python.blah and have it fill in a description and use a template
  • r
    what am i do wrong?
  • k
    Copy code
    - id: pro
  desc: projects
  parent: root
  children:
    - work
- id: work # this matches pro.work.*.python
  namespace: true
  children:
    - python
- id: python
  namespace: true
  desc: python projects 2020
  • k
    you can fix it by removing 
    namespace
    from 
    work
  • r
    Ok so with that i am typiing in pro.work.python.blah and I hit create page but there is no description that is automatically inserted
  • k
    hmm, i think this might be on our end. will take a look
  • r
    ok thanks
  • k
    ran through a bunch of scenarios. in the case where 
    pro.work.python
    doesn't exist, dendron will show you the description
  • k
    after its created, the descriptions will no longer be displayed because we switch to drawing the description from the note instead of the schema
  • k
    you can see that if you create a description in the note and then 
    Reload index
  • k
    going to change the default behavior where new notes will have the description of their schemas (if applicable)
  • k
    just to make sure i'm not completely off the ball, was this the issue you were referring to @User ?
  • r
    Yep you got it
  • k
    @User its been fixed in v0.5.8 which is out as of 30s ago 🙂
  • r
    Awesome thanks!
  • d
    is there a way to make a schema template works on all levels and not just the first one? for example, I created the following schema:
    Copy code
    - id: aws
  desc: ""
  parent: root
  namespace: true
  template:
    id: aws.template
    type: note
    the template works for 
    aws.*
    but not for 
    aws.*.*
    and 
    aws.*.*.*
    and so on
  • k
    to apply schema templates to additional levels, you would need to specify them as children of the 
    aws
    schema`
    Copy code
    yml
- id: aws # this matches aws.*
  desc: ""
  parent: root
  namespace: true
  template:
    id: aws.template
    type: note
  children:
    - quickstart
- id: quickstart # this matches aws.*.quickstart
  namespace: true
  template:
    id: aws.template
    type: note
  • k
    what's the use case you are going for?
  • d
    I want all descendants from 
    aws
    to begin with a "header" as:
    Copy code
    tags: #aws
links:
    so if I create a new item 
    aws.billings.budgets.md
    , it will start with it:
    Copy code
    ---
id: 729433a5-b217-4d65-ab7d-f48581aafbef
title: budgets
desc: ''
updated: 1596641106173
created: 1596641106173
---

tags: #aws
links:

---
    I will use 
    links
    to connect to the parent item, so in this example it will be 
    links: [[aws.billings]]
  • r
    How do you turn on auto suggestions?
  • k
    @User for snippets? schemas?
  • r
    For wiki links
  • k
    - create wikilink brackets and start typing, eg: 
    [[pro]]
    - use the vscode intellisense shortcut (https://code.visualstudio.com/docs/editor/intellisense#_key-bindings) to trigger the autocomplete note: you'll need to start with a naked wiki-link to trigger the autocomplete
12345...757Latest