Add-on store: Improve disk management for launcher and secure copies #14955
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.
Link to issue number:
Part of #13985
Originally raised by @XLTechie in #14912 (reply in thread)
Summary of the issue:
Description of user facing changes
Ensure the caching behaviour of add-ons matches that of NVDA's config.
Files should only be written to disk when not running as launcher nor in a secure context.
Description of development approach
Adds relevant checks to prevent saving the add-on handler state and add-on store caches to disk.
Testing strategy:
Known issues with pull request:
None
Change log entries:
N/A
Code Review Checklist: