Skip to content

Conversation

@modmuss50
Copy link
Member

No description provided.

Copy link
Member

@Juuxel Juuxel left a comment

Choose a reason for hiding this comment

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

This could probably use the problem reporting API too btw, but might be too susceptible to potential Gradle breakages since it's still incubating and this is an important code path

@modmuss50
Copy link
Member Author

This could probably use the problem reporting API too btw, but might be too susceptible to potential Gradle breakages since it's still incubating and this is an important code path

Yes, I did think about using that, and chose not to for that reason. When its stable we can move over to that and centralise all of the deprecations somewhere so its easy to remove them when we finally get around to a 2.0

@Juuxel
Copy link
Member

Juuxel commented Oct 5, 2025

Yeah, I think expanding the LoomProblems class might be a good starting point for it. (There can be a problem group for just deprecations for example)

@modmuss50 modmuss50 merged commit fd2f807 into FabricMC:exp/1.12 Oct 5, 2025
46 checks passed
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