Skip to content

feat!: migrate WebEnhancer to BanManager v8 public API#44

Open
confuser wants to merge 1 commit into
masterfrom
feat/v8-public-api
Open

feat!: migrate WebEnhancer to BanManager v8 public API#44
confuser wants to merge 1 commit into
masterfrom
feat/v8-public-api

Conversation

@confuser
Copy link
Copy Markdown
Member

Summary

  • Migrates WebEnhancer off BanManager's old per-platform event/API classes onto the new v8 public API (BanManagerAPI) introduced in feat!: public BanManager v8 API (BanManagerAPI module + service layer) BanManager#1075.
  • Reworks the platform plugins (Bukkit, Bungee, Sponge, Velocity, Fabric) and listeners (report/ban/denied) to subscribe via the new event bus and call the service facade; removes the now-redundant per-platform BanListener/EventListener shims.
  • Updates PlayerPinStorage / ReportLogStorage and the denied-listener test for the new API shapes; refreshes e2e platform configs.
  • Java 17 baseline (Java 21 to build), matching the upstream change.

Test plan

  • ./gradlew :common:test — denied-listener test updated and green
  • ./gradlew build on JDK 21 (all platforms)
  • Build against BanManager#1075 artifacts, not a published release
  • E2E report/pin flows on at least one proxy + one server platform

Depends on BanManagement/BanManager#1075.

Adapt the WebEnhancer across all platforms (bukkit, bungee, sponge,
velocity, fabric, common) to the new BanManagerAPI service interfaces and
event hierarchy:

- Replace removed per-platform BanListener/EventListener wiring with the
  shared API event subscriptions; report listeners updated accordingly.
- Update storage and CommonPlayerDeniedListener against the new service
  surface; refresh DefaultConfig and the e2e platform configs/messages.

Part of the coordinated v7 -> v8 release alongside BanManager
feat/v8-public-api.
@sonarqubecloud
Copy link
Copy Markdown

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.

1 participant