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
Didn't work when just graph name is given. Also remove test graph that was accidentally checked in
doesn't update its timestamp. Changing a property's core behavior is worthy of a timestamp update
from ref to non-ref e.g. :default to :checkbox created an unusable property type since :db/valueType wasn't removed
Was mistakenly put in because it started with 'property' previously. Also cleaned up get-property-schema since it overlaps with schema-properties and removed an unnecessary use of get-property-schema
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
to their respective ns
of schema. schema concept no longer exists and these old names would be confusing
on a property's page when it doesn't apply there. Also clarify desc so user understands when the configuration applies to a node vs tagged nodes
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
refactor: replace :block/schema with corresponding properties
Fixes logseq/db-test#210. Also fix invalid EDN class db-ident related to this
related to a failing path. Helpfully provides more context and also doesn't misleadingly print tx when it's not related to an import failure with another path
* Add property :logseq.property.table/pinned-columns * feat: table column pinning * enhance: hide :id column by default --------- Co-authored-by: charlie <[email protected]>
Users should be able to use status property independent of Task
Also wouldn't work for priority simple query. Fixes logseq/db-test#207
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.