Closed IAISI closed 6 months ago
Pro Tip! You can help us label your Pull Requests by using the following branch naming convention next time you create a pull request. โค๏ธ Branch naming convention | Label |
---|---|
feature/** |
๐ Feature |
fix/** |
โจ Fix |
chore/** |
๐งน Chores |
api/** |
๐ง API |
performance/** |
๐ก Performance Optimization |
compatibility/** |
๐ค Compatibility |
If your changes do not fall into any of these categories, don't worry. You can just ignore this message in that case! ๐
We have another PR changing this already as said many times on discord. https://github.com/Slimefun/Slimefun4/pull/4120
The https://github.com/Slimefun/Slimefun4/pull/4120 doesn't remove those functions from SlimeFunUtils class tho? If so it's possible they would still be used? By other addons and stuff that is not related to Cargo?
We cannot just remove public API without a deprecation period. The PR deprecates them as is our policy. That PR changes all Slimefun usages of the functions including Cargo.
They will be removed after the next RC when it's merged.
Sounds good, I guess I can just close this?
Closed in favour of #4120
Optimize SlimefunUtils#isItemSimilar Optimize SlimefunUtils#equalsItemMeta
Description
We can skip some of slow ItemMeta checks that relay on getDisplayName() and getLore() which both deserialize string from JSON internally in Spigot
Proposed changes
We check SF Item IDs first if those are available and then fallback to ItemMeta check.
Related Issues (if applicable)
Checklist
Nonnull
andNullable
annotations to my methods to indicate their behaviour for null values