test: Add tests of Obsidian cache with labelled callouts #2905
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:
vault
- improvements to the Tasks-Demo sample vault)Internal changes:
test
- additions and improvements to unit tests and the smoke tests)Description
Cache.test.ts
This does confirm that 1.6.4 could fix #2890 - but only if the user knows that they need to force the Obsidian cache to be updated.
Motivation and Context
Goal: to demonstrate that Obsidian 1.6.4 really did #2890.
It turned out that I had to first make an edit to each of the affected files with callouts that have labels, in order for Obsidian to update its cache.
How has this been tested?
By automated tests.
Screenshots (if appropriate)
Checklist
yarn run lint
.Terms