generated from obsidianmd/obsidian-sample-plugin
-
-
Notifications
You must be signed in to change notification settings - Fork 413
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: Support custom metadata extractors for tasks #2393
Open
aigoncharov
wants to merge
3
commits into
blacksmithgu:master
Choose a base branch
from
aigoncharov:feat/custom-task-extractors
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
import type { InlineField } from "data-import/inline-field"; | ||
|
||
export interface CustomSpecialTaskFieldExtractor { | ||
name: string; | ||
exec: (line: string) => InlineField; | ||
} | ||
export class ExtensionRegistry { | ||
_customSpecialTaskFieldExtractors: Array<CustomSpecialTaskFieldExtractor> = []; | ||
|
||
addCustomSpecialTaskFieldExtractor(customExtractor: CustomSpecialTaskFieldExtractor) { | ||
this._customSpecialTaskFieldExtractors.push(customExtractor); | ||
} | ||
} | ||
|
||
export const extensionRegistry = new ExtensionRegistry(); |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason to expose
extensionRegistry
instead of a direct API calladdCustomSpecialTaskFieldExtractor
is to have a central place for such overrides. I would anticipate more of them to be added later.The long-term vision is for
dataview
to be one and only query engine for any other obsidian plugin. For instance, I would like to completely replace the built-in task querying functionality in obsidian-tasks with dataview.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another potential use-case for the extension registry is to allow for custom indexers - should resolve #1803 without the need to add the canvas support directly to the core.
Overall, the philosopy is to maintain a robust lean core and let third party extensions to take care of new extra features.
WDYT?