Unify method return values in the ObjectLoader class, and simplify how the ObjectLoader is used
#19895
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.
Unify method return values in the
ObjectLoaderclassGiven that all the methods are already asynchronous we can just use
awaitmore throughout this code, rather than having to explicitly return function-calls andundefined.Note also how none of the
ObjectLoader.prototype.loadcall-sites use the return value.Simplify how the
ObjectLoaderis usedThe
ObjectLoader.prototype.loadmethod has a fast-path, which avoids any lookup/parsing if the entire PDF document is already loaded.However, we still need to create an
ObjectLoader-instance which seems unnecessary in that case.Hence we introduce a static
ObjectLoader.loadmethod, which will help avoid creatingObjectLoader-instances needlessly and also (slightly) shortens the call-sites.To ensure that the new method will be used, we extend the
no-restricted-syntaxESLint rule to "forbid" direct usage ofnew ObjectLoader().