Exposing Metas and ParseQueue from Builder #97
Merged
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In some last details, we've ran into 2 things that we need access to that we're continually working around:
Metas- we use these after the build is done to dump some of its data (and some data from the HTML files) into a JSON format that's read programmatically by something else later.ParseQueue- this is useful before parsing happens, so we can accurately print a progress bar that knows how many files will actually be parsed (it may not be all RST files due to caching). Second, it's useful after the build is done so that we can do some post-processing... but can do it only on the files that were actually parsed (and can ignore doing that processing on files that weren't even updated).