We need to extract that upsterParameterizer into a middleware we would pipe into the middlewares for that route. Maybe it is worth to change the name into something generic for write actions.
So that task consists in moving the function into the parameterizers module and inject it properly into the API. Also unit tests for the function should be added.
In the current implementation of the API we have a bunch of code like that:
We need to extract that upsterParameterizer into a middleware we would pipe into the middlewares for that route. Maybe it is worth to change the name into something generic for write actions.
So that task consists in moving the function into the parameterizers module and inject it properly into the API. Also unit tests for the function should be added.