Alexander Söderberg
Alexander Söderberg
Yup. That was poor planning on my part, but then we kind of got stuck with this. This is definitely something I want to improve for v2, as well as...
If anyone can figure out a good solution to this that doesn't inflate the command tree into insane sizes, then I'd be more than willing to add this to the...
> When we use the annotations to set argument, the default value from kotlin declaration is not supported. Default arguments in Kotlin just end up generating overloaded methods. So, in...
Apparently overloads are only generated if you use `@JvmOverloads`. I was under the impression that this was the default behaviour 🥴 If someone wants to go ahead and implement this,...
This should probably be done using a predicate permission. The reason for this is that we need brigadier to filter out the nodes that the sender shouldn't have access to....
A pull request would be appreciated!
> I noticed this too and thought it was intentional. Personally I would do it like so: > > 1. Only show the non-aliases as suggestions by default > 2....
This is because nodes of the same type at the same level are merged into a single node. This is due to the fact that you cannot have multiple variable...
More platforms than Brigadier support suggestions with context, so there should be an option to produce such suggestions. Ideally there'd still be string suggestions that are used by default, and...
Suggestions tooltips are provided for each suggestion, which means they'd have to be provided by the suggestion providers. This is not possible without changing the contract for the suggestion methods,...