API Docs generator performance improvement and bug fixes#2821
Merged
Conversation
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The build was slow because it was opening a new program for every file to generate docs. Now it loads the tool once and reuses it for all files, which is way faster.
Also, some markdown files kept showing up as changed in git even though nothing actually changed (for example: prettier.markdown file appearing everytime the build runs even though no content changes are there). This was because of invisible line ending differences. Fixed that too by making sure all files use the same line endings.
The fix is thoroughly-tested. Safe to merge!