Add NeedPostProcess for Parser interface to improve performance of csv parser and some external parser#15153
Merged
Conversation
Contributor
|
disabling postprocess means you don't get sanitization |
Member
Author
No. sanitization has still been kept. see https://github.com/go-gitea/gitea/pull/15153/files#diff-6e514d0fdd340f9204579f783328a26600737870a4ea70726b5b58ffbe5667f5R94 |
zeripath
approved these changes
Apr 11, 2021
22e32bc to
25207c2
Compare
KN4CK3R
approved these changes
Apr 13, 2021
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.
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.
Before this PR, it took
15sto render a 900 lines csv file with 6 columns on my macOS pro 2020.After this PR, it will spend about
250ms.So
PostProcessis very slow and it's useless for rendering csv file.This PR also make some external markup tool faster to allow them ignore
PostProcess.