Remove mixin filtering - #668
Merged
Merged
Conversation
RyanBrushett
approved these changes
Dec 17, 2021
Member
Author
Not to worry, I have it working but it will have to wait for 0.6.1 😉 |
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
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.
Motivation
It seems mixin filtering is not mature enough yet, and the way we are filtering mixins will end up resulting in RBIs that have some critical mixins missing completely. So in order to not block the 0.6.0 release, I've decided to revert the mixin filtering instead and to focus on implementing it more completely after 0.6.0.
Implementation
Partial revert of #569
Tests
Reverting the test changes in #569