Make jinjajava interpreter render timings trackable..#219
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #219 +/- ##
===========================================
- Coverage 71.48% 71.28% -0.2%
Complexity 1365 1365
===========================================
Files 217 217
Lines 4303 4315 +12
Branches 684 687 +3
===========================================
Hits 3076 3076
- Misses 986 998 +12
Partials 241 241
Continue to review full report at Codecov.
|
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.
Sometime, we want to track the timings of some tags rendering. The application need to provide an instance of the RenderTimings.