In #11508 we switched to a new table component for db graph queries which left
these built-in properties unused. Also moved file query code to
file-based namespaces and fixed a bug where multiple query properties
couldn't be set for a file graph query
Follow up to #11494. Internal ref types are not used in most of the UI
and in any of the outliner layer. Have separate vars for internal and
user ref types so we can see how they're used
* refactor: replace :class/parent with :logseq.property/parent
* replace :class/schema.properties with property.class/properties
* enhance: display schema properties directly in Tag properties
* tag properties style tweaks
* fix: properties view context
* fix: limit parent to be classes or pages depends on the current node
* enhance: display ancestors in Parent
* fix: ancestors
* enhance: display tag properties always for tags
* enhance: display tag block container instead of properties area
* enhance: show add property as popup instead of dialog
* fix: tag parent must be a tag
* enhance: display properties in the right sidebar
* fix: tags style
* fix: icon style
* fix: positioned icons
* fix: lint
* fix: tests
* fix: remove properties from rtc watched attrs
* fix: graph-parser tests
* enhance: style tweaks
* enhance: page/create parses tags from user-input title
* enhance(ux): [[ref]] followed by # (no whitespace) to add tags
* fix: tests
* fix: graph-parser lint and tests
* fix: allow tagged nodes to be parents
* enhance(ux): display tag property descriptions
Also, make it editable.
Removed test as no error handling is needed for ident generation. Also
removed all related downstream uses of catch for
db-ident/create-db-ident-from-name that are no longer needed
- Graphs with description page failed to import
- Graphs that had a page with a built-in class name mangled the block
types. Reverted fix for logseq/db-test#17
- Also updated test for datom count as some parser changes were made
last week to alter it
Only class ident name that wasn't capitalized and didn't match its
title. Considered renaming :logseq.task but unsure if it even makes
sense for their names to match since they aren't sharing a common ns.
:logseq.task may be better off under :logseq.property.*
rRemoving this test as the differences between a file and db graph are
enough that it's not worth testing. This test was helpful when we were
first developing db version
Some block/path-refs were invalid because importer was manually setting
this instead of relying on listeners. Confirmed relying on listeners
works in the frontend and CLI. Part of LOG-3176
