Maciej Laskowski

Thanks for the quick response. I understand and agree with you @soulgalore that adding more magic or additional flags to hide the content between pages in the same iteration could...

Waiting for [Vert.x 4](https://github.com/vert-x3/wiki/wiki/Vert.x-Roadmap#tracing-40)

Hi @scypio, each of repositories have now `knotx-1.x` branch created from `1.6.0` tag.

## Microservices ### Approach 1 - Remote Nodes There is an idea on "Remote Nodes" (just working name) that are actually a Microservices. They can be grouped into tasks as...

Hi @jwadolowski , you may configure what headers are returned by Knot.x Server instance and what are not by overriding `allowedResponseHeaders` in the [`conf/includes/server.conf`](https://github.com/Knotx/knotx-stack/blob/master/knotx-stack-manager/src/main/packaging/conf/includes/server.conf#L19). With that you can achieve the...

@jwadolowski , there might be a solution that Knot.x can technically support. It is a bit simplified scenario in comparison to your proposition: - Knot.x requests repository with `Last-Modified` header....

@plutasnyy I like this idea very much to finally introduce some naming convention for AET suite DSL and attributes. I'm with option to make camel case everywhere. The thing to...

Hi @jwadolowski , I guess that's expected behaviour when screenshot comparison is always green for the very first run of AET (there is nothing to compare, AET just collected patterns)....

Ok, I think I understand your idea better now. I would still try to keep collectors (such as screen/status-code etc.) as simple as possible and avoid extending their logic with...

Idea for a `fast fail` is very interesting. However it is not so easy to define... Please remember that AET tool **does not** detect errors - it detects **changes**. As...