* 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.
Linters are read only by default. Lang lint can be fixed by passing
`--fix`. We don't want CI or inexperienced contributors fixing files accidentally.
Also move deps to bb.edn as putting them inline leads to quirky/buggy
tasks listing and autocompleting as they pause when fetching an inlined dep
Organize them to live under src/main/frontend/worker and add a lint to ensure
that common code with frontend is only under frontend/common/.
Add a linter to ensure that worker doesn't depend on frontend.
Motivated to fix after recent worker breakage fixed by
75463c4df4
class uniqueness was based on the old assumption of :block/name being
unique. This is no longer required for db graphs and case sensitive classes
and properties are now supported
that display all nodes for the current property.
Property pages now behave like classes and display a table instead of blocks.
Also update linter to include objects ns
Was failing b/c property type :page no longer exists. Also added a node
without classes example as it's helpful to test creation and selection
of options for that case
property-value is widely being used to refer to the entity or value
associated with a property entity. Naming the content of a
property-entity :property/value is confusing. property-value content is
a unique name and consistent with :block/content. Also rename related
fns which had similarly confusing names
