that's probably the more semantically correct area. but would not change at this point until we get rid of intermediary dendron config and fix some other warts

just out of priority or are those blocking issues for the change? I personally would say making the config namespace less confusing as soon as possible is higher priority than cleaning up the internals. If adding more migrations complicate the process of cleaning up, maybe I should get to the clean up sooner so we can freely make changes to the configs in a timely manner.

Hi I'm trying to make changes to the nextjs-template package and debug those changes. If I symlink the dendron cli with npm link and run dendron publish dev it pulls the nextjs from github (?). If I cd into packages/nextjs-template and run yarn start it tells me I need a data/notes.json file. I tried to export the JSON of a dendron workspace using the json export pod v2, but that format doesn't seem to be consumed by the nextjs application. Is there instructions somewhere for developing the nextjs app?

Hey, here is the development doc for nextjs : https://docs.dendron.so/notes/PgwAXFfotfgpFVqHQRlBl/

Thank you very much!

is ESM what's blocking us from updating remark?

yes. its not a hard blocker but it might take a sprint to resolve

are you bringing this up for admonitions?

no but there seems to be some drift with commonmark / gfm compliance since we are stuck at a version.

though I would love to see admonitions 😄

got it. i already have a local branch on upgrading remark - currently taking a backburner to the publishing work. aiming to pick that up afterwards

got it. thanks for the update.

I assume there's a plan to swap out the "Show Preview" Editor Actions button to say Toggle now it does that? I checked the package.json and see it in there already but can't work out what triggers only the Show Preview one to display in the editor actions...

yep - we're planning on removing it. wanted to give folks some warning in case they had

show preview

hardcoded as a keyboard shortcut

https://marketplace.visualstudio.com/items?itemName=dendron.dendron-markdown-preview-enhanced This takers upwards of 1542ms to launch. Is this still a necessary extension?

I feel like I can get rid of this at this point

Yeah, that's built into Dendron now, so definitely drop that

this as well I believe?

That is still supported, as far as I can tell, and not merged into Dendron

Info I'm referencing: https://wiki.dendron.so/notes/301e4129-6933-4be7-a4bd-8125171360d8/

Roger roger, not that its my business but maybe removing the MD Preview from the marketplace would be a good idea. It still comes as a recommended addon when installing Dendron and at this point it seems to either be conflicting with other features or not even allowing the application to run at all

don't want people getting a bad experience from it when they're checking Dendron out

I was wondering if I was having LDAP issues at work the other day and then I realized that that extension was causing problems

just because Dendron's boot time in VS Code was significant

Thanks a ton ScriptAutomate!

I just saw this somewhere - I think that MD Preview shouldn't be recommended anymore, at least in new workspaces, due to configs that appear in the code workspace file. New

dendron.code-workspace

files should have a modified

extensions

section like this:

"extensions": {
        "recommendations": [
            "dendron.dendron",
            "dendron.dendron-paste-image",
            "dendron.dendron-markdown-shortcuts",
            "redhat.vscode-yaml"
        ],
        "unwantedRecommendations": [
            "dendron.dendron-markdown-links",
            "dendron.dendron-markdown-notes",
            "shd101wyy.markdown-preview-enhanced",
            "kortina.vscode-markdown-notes",
            "mushan.vscode-paste-image"
        ]
    }

oh my vault is ancient

and by ancient I mean it's a year old but you know, IN VERSION NUMBERS ITS OLD

Dendron moves fast ;P