Update dependency io.github.miniplaceholders:miniplaceholders-api to v3 #33
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 contains the following updates:
2.3.0
->3.1.0
Release Notes
MiniPlaceholders/MiniPlaceholders (io.github.miniplaceholders:miniplaceholders-api)
v3.1.0
Compare Source
Features
Fixes
API Additions
v3.0.1
Compare Source
What's Changed
Full Changelog: MiniPlaceholders/MiniPlaceholders@3.0.0...3.0.1
v3.0.0
: Placeholders Refactor and Expansion Providers!Compare Source
Hi! In this new version, which has been in development since February of this year, several changes have been implemented that modernize the MiniPlaceholders code base, as well as improving performance for both regular and advanced use. In addition to adding ExpansionProvider, a new convention for creating expansions in MiniPlaceholders, without the need to rely on a specific platform.
Expansion Provider
As mentioned above, ExpansionProviders have been added, which are a type of independent project that can provide an Expansion according to the configured requirements. In addition, it is multiplatform and does not require an individual initializer for each platform you want to support. If you want to see an example of its use, you can check out its wiki page or directly review a practical example in the Template Expansion.
Rewritted API Usage
From now on, an audience will not be required when obtaining placeholders. This allows for greater efficiency, as it avoids creating multiple unnecessary objects by delegating the function of providing the required audience to the parsing phase. For this reason, to use MiniPlaceholders Audience placeholders, you must include the Audience in the target field of the
MiniMessage#deserialize
method so that it can be recognized by the corresponding placeholders. In addition, you now have the ability to create type-safe placeholders by including the target class as the first argument. You can find more information about this in the wiki.At the time of writing this changelog, there are more than a dozen expansions already available for MiniPlaceholders v3, such as the PlatformInfo, ProxyConnection, Player, Spark, LuckPerms, PlaceholderAdapter, Vault, and more expansions...
If you liked this update and would like to contribute in some way, we have pull requests available so you can contribute to this project. You can also contribute financially via PayPal or GitHub Sponsors.
Commit Changelog
New Contributors
Full Changelog: MiniPlaceholders/MiniPlaceholders@2.3.0...3.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.