Right now, only a very basic checking is carried out in the summarization parameters when dispatching POST requests. This checks are basically limited to the data type, e.g., the API won't take a "true" as the "relative_max_length", since it expects a float value.
However, following the previous example, the API would not check whether the received "relative_max_length" is ranges between 0.1 and 1.0. Thus, it would take a 999.9 as a correct value.
Expected enhancement: implement robust value checks so that incorrect parameters are detected and ignored.
Right now, only a very basic checking is carried out in the summarization parameters when dispatching POST requests. This checks are basically limited to the data type, e.g., the API won't take a "true" as the "relative_max_length", since it expects a float value.
However, following the previous example, the API would not check whether the received "relative_max_length" is ranges between 0.1 and 1.0. Thus, it would take a 999.9 as a correct value.
Expected enhancement: implement robust value checks so that incorrect parameters are detected and ignored.