Daniel Ennis
Daniel Ennis
Consuming multiple inputs is not something well supported in ACF yet to begin with. > A Switch'ed parameter can be referenced at any location BEFORE its parameterized location or can...
Though I don't mind the idea of moving CommandCompletions to support being placed on the parameter too, but that gets harder to read I'm not opposed to coming up with...
Well you do bring up a good point. For Completions that use context (ie, only show permissions that are allowed/set on the specified res), there is an order issue here....
as a solution for the Async Concern, we can mandate that default params defined at the class level have to be done as a ```java @CommandParameter("param") private CommonParameter param =...
No haven't had time due to other work, but have been thinking on doing some prep work to reorder internals to better prep for this and ease integration with Brigadier.
http://wiki.vg/Command_Data
Reference to luck perms adding support for this: https://github.com/lucko/LuckPerms/commit/c7d2ac956f17bafecc8beabc33111dc224c57935
First pass goal: Register subcommands independently to brig 2nd pass goal: Register parameters with types (string, or primitive) 3rd pass goal: Register static Command Completions to brig as static completion...
lets also make it like manager.enableUnstableAPI("brigadier") so that its opt in until we know its all stable.
Still looking for help here, as I know nothing much about JUnit. We don't need to test Platform Specific. Can create a mock command platform that implements CommandManager and verify...