generated from obsidianmd/obsidian-sample-plugin
-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add "Query File Defaults" facility #3300
Merged
Merged
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
…perty names This makes the names be double-clickable to select the whole property name, which is really nice in Source mode.
I am about to add a lot more cases, and this will be easier to maintain.
This is in preparation for adding another version, for use as a snippet.
So it can be easily added to a callout
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
scope: filters
Additions and modifications to the search filters
scope: frontmatter
Anything to do with YAML frontmatter, also known as Obsidian properties
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.
Types of changes
Changes visible to users:
feat
- non-breaking change which adds functionality)docs
- improvements to any documentation content for users)vault
- improvements to the Tasks-Demo sample vault)Internal changes:
test
- additions and improvements to unit tests and the smoke tests)Description
Introduce a new facility which I have named Query File Defaults.
This defines a set of properties that users can define in a query file to control the behaviour of all Tasks searches in that file:
Document two ways to edit these properties:
Other changes:
widen-property-labels.css
to make longer property names readable in the Properties viewMotivation and Context
I started off by documenting how users could define these variables themselves, and use
filter by function
, but those user queries were going to be so complex and repetitive - to document and to use - that I opted for building-in the facility from the outset.How has this been tested?
Screenshots (if appropriate)
Image caption: Using Obsidian's File Properties to edit "Query File Defaults"
Image caption: Using the Meta Bind plugin's widgets to edit "Query File Defaults"
Checklist
yarn run lint
.Terms