Explore better way to parse search params
Closed this issue · 0 comments
tiagofilipenunes commented
Currently the search params are mostly parsed using validateSearch from an individual route. This has lead to problems namely with limit and offset from the activity pages.
Explore a more generic way to handle and parse numbers so that they don't come as strings or so that a case-by-case validation and parsing does not need to be defined.