Remove Misc class #454
Merged
Remove Misc class #454
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
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #454 +/- ##
=========================================
Coverage 96.64% 96.64%
+ Complexity 2214 2213 -1
=========================================
Files 67 66 -1
Lines 5096 5096
=========================================
Hits 4925 4925
Misses 171 171
☔ View full report in Codecov by Sentry. |
williamdes
reviewed
Jun 1, 2023
Signed-off-by: Kamil Tekiela <[email protected]>
Signed-off-by: Kamil Tekiela <[email protected]>
williamdes
approved these changes
Jun 1, 2023
williamdes
approved these changes
Jun 1, 2023
williamdes
added a commit
that referenced
this pull request
Jun 1, 2023
Pull-request: #454 Signed-off-by: William Desportes <[email protected]>
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.
Follow up from #451 but this time I move the class to
SelectStatementwhere it belongs due to feature envy.