-
Notifications
You must be signed in to change notification settings - Fork 19
Ref: Mixin cleanup #228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ref: Mixin cleanup #228
Conversation
|
I don't know why you would use this over |
0-x-2-2
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of these are wrong, and you shouldn't replace some of these. @Inject is perfectly safe and likely what you want most of the time.
|
Most of this is just abusing the feature. |
|
But many of the old injections were also wrong and should have been using some other feature from mixinextras. |
|
I mistakenly took an error from last year and attributed to |
This reverts commit 4d0eac6.
|
I've tested for potential breaking changes and they're all good |
Due to the nature ofInject, they can cause mixin conflicts with mods that aren't up to date or don't use mixinextra features. This pull request replaces most injections by wrapping operationsThis pull request needs extensive testing as it may break current features and introduce logic bugsThis pull request cleans up the mixins and replaces some mixins with less intrusive ones