"knotx:io.knotx.FilesystemRepositoryConnector": {
"options": {
"config": {
"catalogue": "./library/"
}
}
}
"knotx:io.knotx.HttpRepositoryConnector": {
"options": {
"config": {
"clientDestination": {
"domain": "localhost",
"port": 80
}
}
}
} "knotx:io.knotx.KnotxServer": {
"options": {
"config": {
"repositories": [
{
"path": "/content/.*",
"address": "knotx.core.repository.http"
},
//routing, etc.1.0.0 documentation is here: https://github.com/Cognifide/knotx/wiki/Documentation-1.0.0
there might be small differences - not much changes were since we released 1.0 but there was change in FilesystemRepository (https://github.com/Cognifide/knotx/blob/master/CHANGELOG.md)
hi @malaskowski Thanks for your response. Consider we have search products page which will call third party services(via Knotx) to get the list of products based on user keyword. we have search component to show list of products.
We need to show "add to cart "component(Getting list of sellers via Knotx) for each product. So we added "add to cart" inside search component.
Please provide ur suggestion how to implement this.
If I understand correctly, you have a listing component, that displays a list of products by iterating product by product. Each product item contains an "add to cart" component, that is more complex and requires additional data to work (list of sellers).
Let's distinguish "component" (delivers functionality like product-card or add-to-cart-button) and "fragment" (a part of markup rendered by Knot.x using template engine) first.
One of the approaches would be actually doing the opposite I wrote above. In the latest Knot.x you may combine several components into a bigger fragment, so that your fragment pseudo markup would look like:
<fragment>
<product-listing>
for products in list
<product-card><add-to-cart-button/></product-card>
end
<product-listing>
</fragment>Just note, that processing such a big fragment might be resources and time-consuming, make sure you leverage cache. You may also address this by doing more work on the data before it goes to the template engine module.
Since the Knot.x 2 version you may filter and combine data from multiple sources, even when one source depends on another (e.g. sellers list depending on product details). Using Actions and Tasks you may prepare your data in a way, rendering this markup behaves as the data came from a single source.
Hi All. Hope everyone is fine here. I am facing weird issue on Knotx. Below snippet is added in catalogtitle.jspf which is added in head section of page.
Issue: Below snippet in JSPF file is causing all metatags moving inside body tag from head section. When I remove this snippet, all meta tags are coming to head section.
Snippet:
<knotx:snippet data-knotx-knots="services,handlebars" data-knotx-service=“catalog”
data-knotx-params="{"context": ${contextModel.contextJson}}"
type="text/knotx-snippet">
{{#if _result.success}}
<title catalog-title="{{_result.catalog.title}}">{{_result.catalog.title}}</title>
<meta property=“catalogId" content="{{_result.catalog.id}}"/>
{{else}}
<title>${catalogModel.defaultTitle}</title>
{{/if}}
</knotx:snippet>
1 reply
