Pekka Klärck

I don't like `[ACT]` a marker to end the setup too much. It's not that easy to understand and it would also require big changes to the parser without being...

Implementing the BLOCK syntax would be a somewhat big task in general, but it would be even more work to support it also with setups and teardowns. They currently only...

The problem with assignment as part of `Run Keywords` as well as with setup is that both ``` Run Keywords ${kw} arg AND ${kw} arg ``` and ``` [Setup] ${kw}...

If I understand this correctly, the idea is to report multiple errors from one keyword so that - each error is logged separately and - Robot constructs the final "Multiple...

As you probably already noticed, I submitted #4277 about an alternative way to report multiple failures. That approach would be easier to use because you would use `raise AssertionError(...)` as...

Do you mean both `continue_on_failures` and `robot.api.fail` would be need to accomplish this or that they would provide two alternative ways to do that? I value your proposals, but I...

Do you want both or are you just proposing two alternatives?

So the main idea is adding `robot.api.fail()` that can be called with `continue=True` to make the failure continuable? And then `robot.api.continue_on_failures` context manager would just change the default behavior of...

Do you have implementation somewhere so that I could look at what you've actually done? I cannot think any really clean way how to implement this exact API. I do...

Here's an example of using an API that ought to be pretty easy to implement: ```python from robot.api import logger def kw(expected, actual): with logger.failure_reporter() as reporter: for exp, act...