spike: Experimentally cache data from query.allTasks calculations #3339
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)vault
- improvements to the Tasks-Demo sample vault)Internal changes:
refactor
- non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)test
- additions and improvements to unit tests and the smoke tests)Description
WARNING: this mechanism may be changed or removed at any time: it is not recommended for use by users at this stage.
This is an experimental PR, with work-in-progress, to see if I can speed up custom instructions that use
query.allTasks
to iterate over all tasks in the vault.Motivation and Context
Exploring speeding up the search in:
Once this is merged, I will be able to use it in my own vault, and see if I can:
How has this been tested?
Screenshots (if appropriate)
Checklist
yarn run lint
.Terms