reparse: patch index instead of rebuilding it #501
Merged
+25
−4
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
Following one of the router refactorings (cb0c5c7), the index used in GET/POST requests was immutable, it wasn't replaced by the new index built after reparsing. To fix this, patch the index instead of creating a new one.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #501 +/- ##
===================================
+ Coverage 87% 87% +1%
===================================
Files 122 122
Lines 5119 5127 +8
Branches 1255 1255
===================================
+ Hits 4447 4455 +8
Misses 235 235
Partials 437 437 ☔ View full report in Codecov by Sentry. |
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.
Following one of the router refactorings (cb0c5c7), the index used in GET/POST requests was immutable, it wasn't replaced by the new index built after reparsing.
To fix this, patch the index instead of creating a new one.