Implementation Specific Features

[Sparky983]

With the current architecture of enchanted-shared, it's gonna be pretty challenging for implementations to add their own things. There are currently a few issues addressing some of these problems:

• Subcommand/parameters #32 and feat: add command inspection api #36 - this will allow implementations (and users) to use the metadata from commands in a safer manner.
• Command Return Handling #24 - this will allow again both implementations (and users) to handle the return values of commands. This will most likely be used for the Discord4J implementation as discussed in Discord4J Implementation #9

There are also some issues that require a better way for implementations to interact with the shared-enchanted module to allow for other non-user facing implementation specific things:

• Tab Completion (Paper) #10 - tab-completion/suggestions
• Permissions #8 - permissions
• Alternative Executors #37 - allows for CommandSender, User, etc. This probably won't require a change to enchanted-shared as it will be part of the public API.

[Sparky983]

Forgot to mention, but this issue is for tracking the API of enchanted-shared to allow for implementation-specific features.

Hopefully, this can be completed by 1.0.0, but this issue is pretty abstract so the line of completion is pretty fuzzy.

[Sparky983]

I'm thinking, so implementations can provide their own specific features we could make enchanted-shared just a regular implementation, and all other ones (enchanted-bukkit, enchanted-d4j) to decorate enchanted-shared.

Quick note - enchanted-shared will not be user-facing, so no compatibility will be guaranteed. We may also decide to mark it as @ApiStatus.Experimental because it will have to be published so maven can find it. It might also be useful so others can easily create their own implementations.

I'm also going to start calling platforms implementations just "platform" to avoid ambiguity around whether I'm including enchanted-shared since it is going to eventually be a full implementation.