Shorten the PDFDocument.prototype.fieldObjects
getter slightly
#19903
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.
The effect is probably not even measurable, however this patch ever so slightly reduces the asynchronicity in the
fieldObjects
getter. These changes should be safe since:We're inside of the
PDFDocument
-class and theannotationGlobals
-getter, which will always return a (shadowed) Promise and won't throwMissingDataException
s, can be accessed directly without going through theBasePdfManager
-instance.The
acroForm
-dictionary can be accessed through theannotationGlobals
-data, removing the need to "manually" look it up and thus the need for usingPromise.all
here.We can also lookup the /Fields-data, in the
acroForm
-dictionary, synchronously since the initialformInfo.hasFields
check guarantees that it's available.