Prevent rendering pages without annotations #11
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
Since rendering a page is a somewhat costly operation, pages shouldn't be rendered unless getAnnotations() returns more than 0 annotations. Otherwise, there is no reason to render. This will greatly reduce the processing time, and will likely make the plugin feel more responsive than it currently is.
|
Thanks! Since the original author has abandoned this repo, I had to learn how to build this, with the help of chatgpt, then made the changes you commited to the code and the processing time went from 7 minutes and 40 seconds down to 4 seconds. |
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.
Since rendering a page is a somewhat costly operation, pages shouldn't be rendered unless getAnnotations() returns more than 0 annotations. Otherwise, there is no reason to render. This will greatly reduce the processing time, and will likely make the plugin feel more responsive than it currently is.
Resolves #10