safe-read-string assumed all parsed strings were maps by returning {}
on failure. This could lead to subtle bugs in our new query layer and
other non-map features like hiccup
Looks like the introduction of :logseq.property.view/type
triggered a bug with new pages having the same name as a built-in
and having a page property. This is a followup fix to LOG-3039
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
Bug only triggered by user properties that happen to have same name as a
built-in property and the built-in is capitalized. Added a helper fn to
avoid this bug in the future. Removed hack from #11494 as assuming
a user properties are built-in ones would result in surprised users with
buggy imports. Also fixed lint from previous commit
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
by export rather than listing db-graph properties which would
change a lot. This is a follow up to fixing built-in property conflicts
as part of LOG-3039
New data model of allowing a single :block/type failed a lot of import tx
because properties and class types could be overwritten by a single page ref.
Also this fixes page-properties-tx which wasn't just transacting the
page properties. Also fixes importing pages like 'Tags' which were
incorrectly getting associated to built-in properties with the same name
