Add currentValue to Parameter

[matthiasohst]

In order to set the allowed values independent of the current value used in the returned link, the Parameter class should have a field currentValue which is returned in the get method.

For example, if the field currentValue is added and the line

return allowedValues.isEmpty() ? defaultValue : allowedValues.get(0);

is replaced by

if (currentValue != null) {
    return currentValue
} else {
    return allowedValues.isEmpty() ? defaultValue : allowedValues.get(0);
}

then everything should be working as before, with the option to provide a currentValue different from any of the allowedValues.

[JoergAdler]

Hi @matthiasohst,

sorry for the long time not answering your request.Due to our current workload we cannot guarantee to implement the request.

Would you mind to provide a pull request for this? Maybe with a test, which would explain the issue a little bit more?
As you can always give a current value into the parameter by passing just the object (without constructing a Parameter) into the LinkBuilder I don't get the need for the currentValue field in the Parameter class

[matthiasohst]

Considering the method forCall of the class LinkFactory, the problem is the following: If a CallContext is provided, then the parameters registered in that CallContext must be the ones used in the MethodInvocation.

For example, if the parameter offset is defined and the link is called with offset=10, then the allowed values in the returned schema might consist of just 10 instead of no formal restriction, etc.

This happens in the code:

The value returned by the method get of the class Parameter is used as a key in the map parameters of the class CallContext. This map is used in the method getValues (which is used by getAllowedValues) of the class Scope, where the current value is used as the key. The result is then used in the method createInputSchema of the class RestJsonSchemaGenerator.