A couple of (small) tweaks of the AnnotationStorage
(PR 12173 follow-up)
#12192
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.
AnnotationStorage
-instance, onPDFDocumentProxy
, lazily.AnnotationStorage
to use aMap
internally, rather than a regular Object (simplifies the following points).AnnotationStorage.getAll
returnnull
when there's no data stored, to avoid unnecessary parsing on the worker-thread. This ought to "just work", since the worker-thread code should already handle the!annotationStorage
case everywhere.AnnotationStorage.size
getter, to be able to easily tell if there's any data stored.