Any chance of adding a widget to run other commands? I use an alternate daily note plugin and it would be useful to run that command over.

A lake, mountains and a sunrise peeking through after a moody morning.

#canada #rockies #mountains

I didn't include braces in that example, with the intention of implying that no function call was being made, it appears a no-op statement when reading the code, similar to how a string shows up.

I guess a string is unambiguously a no-op, where my example isn't

I suspect the reason is "directives already existed", and you're preferring to lean on an existing pattern

Eg, something that is statically analyzable, but still clearly compiler magic

import { useServer } from '$compiler/react';

function() {
useServer;
// ...
}

The "use strict" directive was deliberately backwards compatible. I wouldn't expect the same for code that uses "use client" or "use workflow".

If compilation is a requirement, why not skip the backwards compatibility and use syntax that could handle versioning, namespacing, etc.

AP and AT have different goals, and AT is still building its core functionality, eg, hosting private data on-network. The usability of spinning up new AT clients isn't really a central tenant of AT, unlike on AP where creating new nodes is one of the main selling point.

Beard Doyle

Jagged snow-capped mountain peaks, rocky slopes, and teal glacial lakes.

#MountainMonday

It's wild that daily note rolling-over isn't built into the core plugin.

This brings the functionality closer to something like Notion "relations" or Dataview plugin. Bases can show properties from multiple different files and treat your vault like a queryable database.

"You can now also access properties from a file reference." You make my dreams come true. ❤️❤️❤️

@obsidian.md The "Functions" docs suggest that I should be able to access a file when creating a formula with `file("somefile.md")`, but I'm just getting "⚠️ Error" in the field. Am I missing something?

I'm very excited for the potential of reading frontmatter from other files. Joining content between bases would open a lot of doors, similar to Notion's relation fields.

Does your day-to-day result in notes primarily time-stamped in this format? Or do you try to name files uniquely? I suspect that I'd routinely run into naming conflicts with a flat structure like yours.