WIP - New API #3243
Draft
WIP - New API #3243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR initiates the development of a new API as outlined in #2996, aiming to improve the overall maintainability and flexibility of ProtocolLib. As this is the first draft, backward compatibility may be (temporarily) broken, and it will primarily serve to track progress and gather feedback on API design and concerns. The PR will remain a work-in-progress until all current features have been incorporated into the new API, with stability and structure refined for broader usage.
I encourage everyone to participate in shaping this new API. If you have suggestions, concerns, or alternative approaches, feel free to contribute your thoughts. Feedback on design decisions, modularity, or areas where backward compatibility might be preserved is especially welcome. This collaborative effort will help ensure the API meets the needs of both current and future developers. Please don’t hesitate to recommend changes or improvements as we refine the API together.