2022-02-16 Office Hours

Office Hours

February 16th, 2022

Release notes:

• 0.81: https://wiki.dendron.so/notes/E1Zgn2za7n3QVfm3MtIBe/
• 0.82: https://wiki.dendron.so/notes/egxM8X43CqrQLuhYQ6Wu8/

Highlights

• CURRENT_WEEK now an option in Schema Template Variables
• Cross vault link syntax for template values in schemas
• Pods v2: In preview! Can enable, test out the Markdown Export Pod, and try out the new Airtable Export Pod
• Workspace Sync improvements

Notes

• Seed onboarding repo is a good playground to try features out: https://github.com/dendronhq/seed.dendron.onboarding
• Cross vault link syntax
  • Ensure that you're always using the right template even if you add new vaults over time
• Airtable Docs:
  • https://wiki.dendron.so/notes/oTW7BFzKIlOd6iQnnNulg.html#boolean

Q&A

• For questions, please add your @{discord-handle}: question
• @kevins8 (Private): how do I ask questions on the google doc? (example)

Notes around questions asked during office hours

1. @ThatSisyphean (Private)#7459: Can you use checkboxes for inserting booleans into Airtable?
2. Example of how I’ve been formatting things:
3. 
4. The tags.v hierarchy is a set of variables that I’m keeping track of
5. I’d like for some of these variables to be sort of Dendron environment variables that I can update the value of from anywhere in the note hierarchy
6. Use case: keeping track of how much money my DnD character has
7. In the DnD session notes I could just type #v.money (Private): +2 and it would add 2 monies to the v.money variable.
8. My use case is niche, but I could see other people coming up with much cooler stuff.
9. Not sure if this is worth the effort of implementation cause you’d have to serialize the variable changes somehow. Not sure if non-commutative operations would be possible unless you had an order in which the variable was changed. And then you run into issues where the variable isn’t the correct value you know it should be and you have to scour notes to find why it’s wrong.
10. Other variables just represent a cell in a row in a DB.
11. The note itself is the row ID and the variable is the column ID
12. When rendered in Obsidian’s mobile app, this becomes just a real simple form to fill out.
13. I’m thinking the benefits here might be limited though since airtable already has a decent form interface and you’d be replicating data in multiple places (the dendron note and the airtable entry)
14. It would be cool to build the form in dendron like this rather than going through and manually making airtable tables and bases. You’d lose some advanced Airtable functionality I assume in exchange for convenience.
15. Regardless thanks for all the work
16. Final note is that syncing these “dendron forms” between devices is a pain especially because you can’t create a note on mobile.

Comments

• Hyun Ik Choi: I just checked this. This is part of the sanity checking logic in the publish commands that didn't get cleaned up. Thanks for bringing this up. This should be removed.