Skip to content
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

Deprecate bundled item data #2514

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

me4502
Copy link
Member

@me4502 me4502 commented Apr 18, 2024

This PR deprecates the concept of bundled item data, as well as the concept of "item material". This was added but never actually used. It's not very mod-compatible, and also requires storing increasingly large numbers of JSON files within the repo and jar files.

Due to the fact that WorldEdit never uses these at all, and that the bundled item registry is loaded when first accessed, this means we can remove the call to actually load it from WorldEdit. If something does happen to be using this deprecated API, it'll trigger it to be loaded upon first access.

@me4502 me4502 requested a review from a team April 24, 2024 10:21
@me4502 me4502 added this to the 7.4.0 milestone Apr 24, 2024
@me4502 me4502 force-pushed the chore/deprecate-bundled-item-data branch from 0c91194 to 9834d08 Compare July 12, 2024 10:45
@me4502 me4502 requested review from octylFractal and a team July 12, 2024 11:12
@me4502 me4502 force-pushed the chore/deprecate-bundled-item-data branch from 9834d08 to 873b2ed Compare October 27, 2024 06:48
@me4502 me4502 enabled auto-merge (squash) October 27, 2024 06:48
@@ -65,6 +65,7 @@ static URL loadRegistry(String name) throws IOException {
}

private final BundledBlockRegistry blockRegistry = new BundledBlockRegistry();
@SuppressWarnings("removal")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we deprecate this field / the related getters in this class?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can deprecate the field, but we cannot deprecate the getter currently because that propagates it to all classes that extend this, and would lead to non-deprecated methods getting marked as deprecated.

we currently can't remove this from the inheritance tree, so it's not really an option to deprecate this currently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants