Is possible to allow clicking a property and be able to go to a page with property’s name and have al pages using such property as back reference links. Roam allows this.
It’s useful to browse all properties vales and where they are used in.
A question? How to differentiate between user properties (my domain properties) and program/future plugin properties?
For example, if I want a property named collapsed be attached to a block because has a meaning to me in the context of the content of a document. How to do that and don’t cause problems with internal collapsed property used by block collapsing?
Also, in the future, If I’m using a property named abc and some future plugin uses it for another thing, how can we handle these conflicting situations?
And if Logseq supports clicking a property (like a page) to show linked values and pages (like Roam does), Logseq and plugins properties should be forbidden to do that operation (or at least a plugin can allow some properties to be clicked and others not).
What about using some type of prefix/namespace for properties to indicate when a property is an user property, a logseq/plugin property not treated as page and one that can be clicked like a page?
user property: abc::, hij::. First character cannnot be an underscore “_”
logseq/plugin property (not clickable like a reference): _ls-core-collpased::, _ls-pluginnamespace-propertya::, etc. Starts with underscore “_”
logseq/plugin property (clickable like a reference): ls-core-collpased::, ls-pluginnamespace-propertya::. If an user types a property startting with ls- must to know that in the future can have conflicts with logseq or plugins properties.
Where is this documented aside from a mention of a canary release from over a year ago? Throughout the main logseq documentation the use of colons is inconsistent and the optional title and body are nonexistent (as far as i can tell). Am I to understand this would all go in a single block (with no bullet points to the left of it)?
Not really, sorry - I could find this page and did read it, but where is the documentation about the optional title and body before and after the properties in the same block? I know i saw that somewhere but it’s not clear from here.
I’m interested in learning more about what @Zab asked. I want to compute and store some meta data on pages when they’re updated from a plugin. Ideally I’d like this data to be hidden from view, and in a namespace belonging to the plugin. Is this possible @tienson ?
Also curious if there is any size limit for how much data I can put into a property?