-
When service has missing configuration following error occurs during fragment processing:
`java.util.NoSuchElementException: No value present
at java.util.Optional.get(Optional.java:135) ~[na:1.8…
zajcu updated
7 years ago
-
JSON configuration with verticles is quite complex. Knot.x provides two configurations: knotx-standalone.json, knotx-example-monolith.json. We need to design how to split those files to more managable…
-
Fragment Assembler merges all fragments into a client response. Default strategy "UNWRAP" requires two performance improvements:
- use fragment.isRaw() instead of `FragmentConstants.ANY_SNIPPET_PAT…
-
Headers are not propagated from the client request to the repository request. Configuration change does not fix the issue.
-
We need add documentation with:
- how to set up project in IntelliJ and debug code
- how to connect to verticle with remote debugger
-
## 1. Server Verticle configuration
``` json
"server" : {
"config": {
...,
"repositories": [
{
"path" : "/content/local/.*",
"address" : "knotx.filesystem-re…
-
# Overview
This issue is described in https://github.com/Cognifide/knotx/issues/213. This task needs to address all points:
- Change Fragment model to support Knot configuration
- Update example co…
-
In many cases using `` tag name is problematic. We could change it to more custom name like:
``
-
Implement custom Knot.x tag `` that will enable _routing_ control inside snippets.
Inside the tag developer may put `json` configuration that defines routing basing on adapter services responses.
Hier…
-
Custom tags will be placed inside snippet and should be interpreted by Knot.x Templating Engine after Handlebars processing.
Inside custom tags developer will put JSON object that describes tag config…