Add allowAnyValue - #576
Conversation
Sorry, something went wrong.
Added a new option: allowAnyValue
Co-authored-by: DerEchtePilz <81232921+DerEchtePilz@users.noreply.github.com>
Co-authored-by: DerEchtePilz <81232921+DerEchtePilz@users.noreply.github.com>
Updated to add exception if non-string mappers are used
| * @return this list argument builder | ||
| */ | ||
| public ListArgumentBuilderFinished withMapper(Function<T, String> mapper) { | ||
| if (allowAnyValue && !(mapper instanceof StringTooltip)){ |
There was a problem hiding this comment.
This instanceof check is not necessary as it will always evaluate to true.
Sorry, something went wrong.
| */ | ||
| public ListArgumentBuilderFinished withMapper(Function<T, String> mapper) { | ||
| if (allowAnyValue && !(mapper instanceof StringTooltip)){ | ||
| throw new IllegalArgumentException("allowAnyValue cannot be used with non-string mappers"); |
There was a problem hiding this comment.
I'd say this should be something like:
allowAnyValue can only be set to true if a String mapper is used.
However, I do not know if that even is better so maybe we could wait for other opinions too.
Sorry, something went wrong.
| // should only be used with string mappers so we can ignore the cast warning | ||
| list.add((T) str); |
There was a problem hiding this comment.
| // should only be used with string mappers so we can ignore the cast warning | |
| list.add((T) str); | |
| list.add(values.get(str)); |
As we have the map, I think we should use it instead of resorting to generic casts.
Sorry, something went wrong.
There was a problem hiding this comment.
@DerEchtePilz when I use the mapper it will give me a list of nulls. The only way I've found that works is to directly cast the string to T.
Sorry, something went wrong.
There was a problem hiding this comment.
Well, that sounds like a bug to me that should get fixed. I am currently not available to test anything related to the ListArgument but using the mapper should most definitely not result in null values.
Sorry, something went wrong.
There was a problem hiding this comment.
I'm not sure if it's a bug but maybe just a design flaw. The mapper value only works if the input is in the suggestions list.
That part might not be compatible with what we're trying to accomplish so that's why we made allowAnyValue only valid with strings since we need to cast the string input to T.
Sorry, something went wrong.
| // should only be used with string mappers so we can ignore the cast warning | ||
| list.add((T) str); | ||
| } | ||
| else{ |
There was a problem hiding this comment.
| else{ | |
| else { |
Sorry, something went wrong.
|
|
||
| $$\downarrow$$ | ||
|
|
||
| > ### Allowing any value (Optional) |
There was a problem hiding this comment.
In this section I think we should mention that the allowAnyValue option only works for Strings.
Sorry, something went wrong.
Added a new option: allowAnyValue
This allows me to use ListArgumentBuilder for complex tab suggestions and simply passing all input so I can do my own validation.
This allowed me to create this command: https://youtu.be/q03_paw9Vzk