Maybe the inline properties can be mirrored and synced to YAML properties?
That way they can be cached like the other YAML properties and won’t cause any performance issues. (Unless the syncing/mirroring itself causes slowdown)
In a related note, being able to create “sections” inside YAML would go along with this nicely. i.e. Having a “Inline” section of the YAML.
Or much simpler, just having the ability to hide some plugins
IA Writer has a feature like that: https://ia.net/writer/support/editor/metadata?tab=iphone#document-metadata-iphone.
I’d like things to be fast, but I think fast can be worked around whereas duplicating values between inlines and frontmatter is a clumsy editing workflow. Removing inlines also makes it impossible to support smart calculator-like notes, think recipes or long calculations with intermediate values.
Right now with Bases I’m having to make a choice between duplicate all my properties (ugly and risks divergence on edits), rewrite all my properties (hard to undo), or not use Bases for most of my notes.
I think the cleanest way to implement inline properties is with the existing Dataview syntax:
(inline:: value) only renders value.
[example:: value] which shows example value.
Totally agree - If it is a toggleable option at the app level, ok.
I used DV extensively years ago and, at some point, need to remove the litter with linter. I found block level links provide me with all the power I need for my use of Obsidian.
Bases is not dataview - if I’m not mistaken, even DataCore is advising against inline fields. Sorta handwriting on the wall.
Oh, that’s cool. Sometime I use IA Writer to write on my Obsidian notes and I didn’t know that. So… maybe Obsidian could adopt the same syntax 
?
If they do the feature, it would for sure be nice to use an existing syntax.
Just tried usingBases as a sidebar widget to surface tasks and discussion points tied to specific people but failed b/c I realized my existing flow with inline links was a Dataview feature 
I currently have a workflow where I set tasks like:
- [ ] (with:: [[John]]) Follow up on X
Then in John’s note, I use a Dataview query like:
TASK WHERE contains(with, this.file.link) AND !completed SORT file.name ASC
That works perfectly. Dataview recognizes the inline field and link relationship, so I can see everything I’ve marked “with:: [[John]]” across my vault.
If Core (and therein Bases) could read and filter inline fields like with:: [[John]], it would effectively enable relationship-based dashboards right inside Obsidian — similar to Tana’s sidebar views which is something I really miss.
This would open up powerful use cases:
Something to also consider building or perhaps extending with Dataview library when Base API is released.
extra…would be great if you could control what Bases were activated based on which tags the current note you were on to build dynamic views.