those PRs fix problems with the configuration and the correct form encoding (for "application/x-www-form-urlencoded")
@nowszy94 Please check out this article: https://github.com/Cognifide/knotx/wiki/HandlebarsKnot#how-to-extend
you may create custom handlebars helper
merged: Cognifide/knotx#257
For instance, on the adapter verticle, add option logActivity: true on clientOptions object, as follows
"options": {
"config": {
"clientOptions": {
...
"logActivity": true
}
}
}then in logback.xml set DEBUG level for netty handler:
<logger name="io.netty.handler.logging" level="DEBUG"
additivity="false">
<appender-ref ref="STDOUT"/>
</logger>
I tweaked the REST service example to support filtering by a keyword provided by the user and added an option to limit the number of results by means of an HTML form present on the same page. I'd like to display this metadata but the response from the Google Books API doesn't contain it and I don't know of a way to access it in Knot.x itself.
Is it possible to refer to the query string or form parameters inside a Template?
@toniedzwiedz it is not possible currently to access query parameters inside the template, however you have full access to query parameters inside Adapter via ClientRequest object
in template, you can operate over _result (contains data from service call) and _response (contains service response metadata, as e.g. status code) scopes
Maybe it is a good idea for an improvement, to enrich metadata by e.q.
_request with request parameters - guys what do you think?
this movement simplfies a lot of things like: reviews, collaboration etc
You can check our blog post with scenario that's closer to the real setup http://knotx.io/hello-rest-service/