I think most approaches to this kind of thing make the file fundamentally a markdown file. Or if it's a code file, it's a doc tool. Maybe there is a doc tool with a VS code extension. I'm just inspired by Dendron's lightweight approach. If you can view your file in your IDE, and export a website, that's all you really need (is the insight)

I suppose I could write my own extension (but sounds like more of a learning curve)

A specific question would be: where does MPE intercept scrolling

or can I configure VS code to activate an extension for files of a certain type. if this is too off-topic, no worries

ah darn I'd have to patch this line: https://github.com/shd101wyy/vscode-markdown-preview-enhanced/blob/701ac943c303088fa349d38d19fdd5736e1e0a72/src/preview-content-provider.ts#L856

patching mpe for non-markdown is an interesting idea. you can override the language id of a doc in vscode which might be enough to make mpe recognize, for example, ts files

the only problem is I'm assuming I also definitely want the lang to be TypeScript, so the buffer is treated as a TypeScript file for all other purposes

hm unless I did something funky like point two workspaces at the same file tree, heh, with different file extension to language mappings

for now, I am just writing Markdown docs in separate files from the code and tabling my literate programming dreams for the time being

Did something change with the way templates are handled in the last few days? Maybe part of the server upgrade? Here is my setup: `journal.schema.yaml`:

- id: journal
  parent: root
  children:
    - daily
- id: daily
  namespace: true
  template:
    type: note
    id: journal.template.daily

journal.template.daily.md

---
id: 8e98e784-d8b3-458d-bf7b-f84f013455c9
title: Daily
desc: ''
updated: 1601739257799
created: 1601739257799
stub: false
---

#### Tasks

#### Notes

#### Plus / Minus

#### Next

This worked as expected on 2020-10-28, but did not do the template expansion on 2020-10-29. I did change the

dendron.defaultJournalDateFormat

because the server upgrade changed it to

Y.MM.DD

. Nothing useful in the logs. Does anyone have any suggestions?

Hmm

just verified, mine still applying

and I have similar schema and template

Ah, thanks for checking.

Still...

so what is your

dendron.defaultJournalDateFormat

config set to currently

I flipped it back to the previous default:

"dendron.defaultJournalDateFormat": "Y-MM-DD",

So you do not want the hierarchy by year/month/day? Clarifying to make sure I understand

As far as I understand the - annotation will not provide parent/child for the year to month to day

No, I guess I could, but I have a bunch of notes I would need to rename.

Oh I gotcha... saying that you changed the setting since it was changed in the update?

To be consistent with your existing notes

I have a ton of notes in ISO 8601 format

gotcha

So currently you create a new journal note... with keybind and it creates the note, names it as expected 2020-10-29 but does not populate the template?

Er 30 I guess... time flies when I am having fun

Ah, I think I figured it out. All my schemas seem to be missing the following:

version: 1
schemas:

If I add that, I get back to the working behavior. TIL

Thanks for poking at it as well 🙂

Yep no problem. Wonder how mine had it... I think my vault/workspace initiated more recently than yours?

I do remember Kevin mentioning that now that you came across it, doh