Implement and Test NFR #10866

[lajosbencz]

NFR #10866

[andresgutierrez]

This looks too arbitrary, not sure if everyone wants to ignore empty strings #440

[sergeyklay]

Mb

return filter->sanitize(defaultValue, filters);

?

[lajosbencz]

Makes sense!

[lajosbencz]

Imho, I can't really think of a case when a 0 length dispatcher param is useful after sanitation... not that others can't, but one will most likely handle it somehow, or just skip a prog branch. I think it's counter-intuitive if one still gets an empty string if a defaultValue is provided.
If only sanitation is the objective, defaultValue can be left empty.
I'm not keen on this implementation, because I don't need it in any project atm... nor is it something cardinal. It just makes sense for me this way :)
Also, dispatcher is a bit different than models or forms.

Sticking with the Mvc implementation, consider these (albeit limited and not allowing for proper routing patterns) examples for int validation:

• user/view/123 will display user from db
• user/view/awd will get any empty string as id, there will be no returned rows. Page will either be left empty or routed to 404 with if/else
  Although these cases will not benefit from a defaultValue, but I don't think the developer would provide one in the first place.
• category/view/123 proper page is displayed
• category/view/awd There would be no rows. Now defaultValue can be useful, instead of displaying a not found and handling it with if/else, developers could provide a defaultValue for a common/promo'd category.

[lajosbencz]

On second thought, adding a hasParam method would also allow for more flexibility without any impairment