Feat/db #66
Open
Feat/db #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bad3r
force-pushed
the
master
branch
2 times, most recently
from
4c12d03 to
6244543
Compare
Bad3r
force-pushed
the
master
branch
4 times, most recently
from
9a2e078 to
458ac81
Compare
tiensonqin
force-pushed
the
feat/db
branch
2 times, most recently
from
ec41c85 to
b66a3b8
Compare
In some contexts silent failure will seem like a bug as new users may try to accidentally use or create some of these
Also bring back page test helper which doesn't have file graph assumptions
imported property should behave like app
imported tags should behave like app
Also fixed using pages as a tag first time via '#' didn't build tx correctly. Fixing these allowed for enabling logseq.class/Page validation
* perf: add frontend.handler.profiler * perf: add frontend.components.profiler
Feat: support plugins for web
since the last export.
Related to new fix-block-timestamps! in migration
relationships from table view. This would break major internals if delete actions were done on logseq.class/Root or most built-in properties
Was possible to delete built-in closed values from queries like `(property :logseq.property/created-from-property)`
after type->tags migration. Also update recommended validate cli options to default to true. Also clean up graph counts spread across two validators and importer. The property-pairs count in the UI were way off because they were only counting pairs that are validated by malli-schema
* Schema update for property history * feat: record property history * Initial support for time tracking * enhance: status history view * fix: reactive time tracking * fix: tests * enhance: set max height for status history * enhance: disable some options for property enable-history? * address suggestions from zhiyuan * fix: spent-time for doing tasks * enhance: status history support reverse order * chore: merge feat/db
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.