Open metas-dh opened 6 years ago
That's happening because frontend transmits the valueTo as '' (empty string).
It shall send null
.
I can't reproduce this. Since this was fixed on the backend I guess we can close it, right ?
I guess we can close it, right ?
yes and no. I mean:
yes can close it with "won't fix" resolution because even if the frontend is still sending valueTo:""
, backend defensively ignores it.
no we cannot close it because the actual task requirement was not solved. i.e. frontend is keep sending valueTo:""
.
Just reproduced now on w101:
let's lower the priority because is no longer a show stopper and we shall fix it in future.
Is this a bug or feature request?
Bug
What is the current behavior?
When you change the filter params sev. times, the results are not correct.
Which are the steps to reproduce?
What is the expected or desired behavior?
Shall work.
LE: because of https://github.com/metasfresh/metasfresh-webui-api/issues/1102, the effect of this task is canceled, but the requirement of not sending
valueTo:""
remains.