Parameter Switches

Implement @Switch(“res”) to be used such as:

@Subcommand("set")
public void onResInfo(Player player, @Switch("r,res") Residence res, Permission perm, PermissionState value) {
  res.getPermissions().setState(perm, value);
}

With this, the following commands should work:

/res set 1111 build true
/res set build -res 1111 true
/res set -r 1111 build true
/res set build true -r 1111

When a parameter has a switch, it can be “Supplied” at any location of parameters (but not before the subcommands)

Switches should process command replacements

We can achieve this by first pre-parsing all switches during context resolution, marking what parameters have been satisfied, and then iterating the remainder of unsatisfied to complete them in order.

No new registration of switches needs to occur.

Switches should use - prefix by default, but the manager should allow customizing switch prefixes.

[bundabrg]

I ended up implementing it in my own command parser (Docs) mainly for fun.

[heroslender]

Is this feature still being worked on? Saw the PR but there’s no activity there for over 2 years 😕

Also, would it be possible to use boolean @Switch without the the need to specify the value? For example: /foo -s would result in the Switch s being true, and /foo would result in s being false, wich could be obtained with the use of @Default("false").

The problem would really be the 1st one, maybe make it so that boolean switches don’t have a input value.