that are now obviously file graph specific
- mv save-tree! as it calls file-handler/alter-files via events
- mv roam import which called file-handler/alter-files
- mv git component which is only enabled for file graphs
- fixed handler.code which allowed db graphs to call file graph code for
an edge case
* wip: view group by
* feat: view group by rendering
* enhance: use current group's value when creating new block
* enhance: add icons for view layouts
* fix: group rows selection
* fix: property type migration from #11695
* refactor: use namespaced keyword for block export
instead of confusing :build/block. Also improved related tests,
simplified import steps, added some missing sqlite.build docs,
and fixed :build/uuid not working for some existing journals.
* fix: remove export+imports invalid
when uuids are kept and when journals are created.
Also removed :logseq.class/Journal from export as its needless noise
* fix(ux): incorrect behavior for the sub menu content within the table header popup
* fix: group rows delete
* fix: lint
* fix: group block delete
* fix: bump version
* fix: group by titles not correct for :checkbox
Also enable group-by for :date as they just work
* fix: disable nonsensical and unreadable groupings for :many properties
* fix: grouping not working for :default property type
and sometimes :number or :url.
Was grouping by entity and not what user reads. If there are
2 :default values with 'text ha', this seemed buggy
* fix: icons not showing for grouping by status
---------
Co-authored-by: Gabriel Horner <gabriel@logseq.com>
Co-authored-by: charlie <xyhp915@qq.com>
as it also belongs to tasks. Also tweak language so that it also starts
with 'Repeat'. Using consistent language helps users understand behavior
that changes depending on configuration
Now that schema is no longer a persisted concept there is no need
to spread built-in-properties keyword mappings across the app.
Doing so makes built-in-properties more rigid as it would be
needlessly coupled to the frontend, exporter and migrations.
With this cleanup it'll be easy to deprecate :schema from
built-in-properties when we need to
Since #11673 will provide a lower level public? property,
made sense to rename to avoid confusion between public and public?.
Also start deprecating :name config in built-in-properties as it
is barely used and is somewhat confusing
Properties and class pages have critical info in their properties.
When reading on a published site, it's bad ux to have this useful info
hidden on hover
