This repository was archived by the owner on May 7, 2025. It is now read-only.
Open
Conversation
…after doing so. This provides plugin resource fetchers a hook to do some additional processing when fetching internal resources. For example, a resource fetcher might batch up the requested files, and process them all in one go.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This pull request is Finalized
Related issue(s) and/or pull request(s)
See also #144*
Test cases, sample files
Additional information
Provides additional events to be emitted when resource fetcher is getting internal resources (files listed in the HTML of the chapter) and for files embedded in the css file(s).
The Bibliotheca hybrid app uses this to help it's resource fetcher plugin batch up file requests. Essentially, when the start event is emitted, it begins a batch; then individual file requests are queued up. When the end event is emitted, it sends the queued up list of files to the API, which reads the contents of each specified file and returns the contents as a response.
This helps to make the resource fetcher more performant because it limits the number of requests sent across the wire.