chore(plugins): Do not depend on AnalysisBasePluginAdapterMixin
#1328
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
The mixin is an internal thing that should not be used in plugins. Moving it in the abstract class, allows us to silently remove it in the future.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1328 +/- ##
==========================================
- Coverage 92.48% 91.84% -0.64%
==========================================
Files 379 376 -3
Lines 24115 21038 -3077
==========================================
- Hits 22302 19323 -2979
+ Misses 1813 1715 -98 ☔ 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
3 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.
The mixin is an internal thing that should not be used in plugins. Moving it in the abstract class, allows us to silently remove it in the future.
@jstucke Iirc, we discussed this some time ago but apparently forgot to ever to this :)