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

Mark paper-plugin.yml as experimental #2122

Conversation

lynxplay
Copy link
Contributor

@lynxplay lynxplay commented Sep 4, 2023

While paper plugins and their respective loading strategy have been integrated into paper for a while now, the developer facing side of paper plugins is still highly experimental.

Specifically the paper-plugin.yml file structure is still under active development and its syntax might change without a deprecation cycle. Its usage for general purpose plugin development is still hence discouraged.

While developers that are familiar with the caveats of using paper plugins but decide to do so anyway due to the already existing features exist, this commit still adds a warning to ensure that developers not familiar with the system do not accidentally use it for new projects, preventing frustration down the line with potential missing features or breaking changes over the usage of a plain plugin.yml file.

@lynxplay lynxplay force-pushed the enhancement/mark-paper-plugins-as-experimental branch from 193ba10 to 1d8cd79 Compare September 4, 2023 21:48
@lynxplay
Copy link
Contributor Author

lynxplay commented Sep 4, 2023

Resolved formatting issue.

@Earthcomputer Earthcomputer requested a review from DenWav September 9, 2023 05:42
While paper plugins and their respective loading strategy have been
integrated into paper for a while now, the developer facing side of
paper plugins is still highly experimental.

Specifically the paper-plugin.yml file structure is still under active
development and its syntax might change without a deprecation cycle.
Its usage for general purpose plugin development is still hence
discouraged.

While developers that are familiar with the caveats of using paper
plugins but decide to do so anyway due to the already existing features
exist, this commit still adds a warning to ensure that developers not
familiar with the system do not accidentally use it for new projects,
preventing frustration down the line with potential missing features or
breaking changes over the usage of a plain plugin.yml file.
@lynxplay lynxplay force-pushed the enhancement/mark-paper-plugins-as-experimental branch from 1d8cd79 to a81e7a8 Compare October 8, 2023 10:09
@RedNesto RedNesto merged commit 2968496 into minecraft-dev:dev Dec 7, 2023
4 checks passed
@lynxplay lynxplay deleted the enhancement/mark-paper-plugins-as-experimental branch December 8, 2023 18:23
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.

3 participants