The parameter objects are great to have a reasonable route method signature.
However, what is lost is the documentation of the API tool.
You can see this happen in a sample project: jooby-apitool-param-obj
At the moment we're working around this by writing custom ApiPaser, ApiProvider and ApiTool and annotations to hack our way around this using reflection. This will be difficult to maintain as Jooby upgrades.
I think there must be other projects which use the same method of accepting many GET params, and losing the documentation tool.
What do you think?
The parameter objects are great to have a reasonable route method signature.
However, what is lost is the documentation of the API tool.
You can see this happen in a sample project: jooby-apitool-param-obj
At the moment we're working around this by writing custom ApiPaser, ApiProvider and ApiTool and annotations to hack our way around this using reflection. This will be difficult to maintain as Jooby upgrades.
I think there must be other projects which use the same method of accepting many GET params, and losing the documentation tool.
What do you think?