Closed TheBusyBiscuit closed 4 years ago
Please dont change the way our imports are listed will dl a full review tommorow
I only removed unused imports for the most part, in many classes you are importing like 10 classes that you don't even use. In some occasion the import order might be slightly changed, but mostly it's the removal of unused imports. I suggest to leave it like that, since you are enforcing the google java style guide as per contributing.md I wanted to PR an auto-import fix github workflow next anyway, so you won't ever need to worry about imports anyway, neither unused nor order.
The auto-import workflow would be great And what contributing.md are you talking about
Oh nevermind, you don't have that file. I was referencing this comment: https://github.com/J3fftw1/LiteXpansion/pull/48#issuecomment-687542230
Okay then lets leave it like this also could you link me to the workflow i wanna read up on it
I already made a PR for it #92 It just runs the official Google Java Formatting jar from Google with the "fix-imports-only" setting.
Conflicts
Any weird imports, the workflow will take care of :P
See :D
Short Description
This fixes the Exception which is thrown when the Enchantment is already registered (usually only on reloads). While reloading itself is discouraged, we can and might still fix this exception.
Also updated to RC-17, included the LICENSE in the compiled jar, finally implemented bStats properly.
Related Issues
No currently open Issues I think
Checklist
Nonnull
andNullable
annotations to my methods to indicate their behaviour for null values