Pekka Klärck

Sorry for dropping the ball on this. If someone is interested to continue with this PR, or possibly create a new one, there would be still time to get it...

We are planning add support for library keywords with both embedded and normal arguments (#4710). It has two implications related to this issue and the example in the description. First...

As explained above, the example in the description won't work anymore if #4710 is implemented. I recommend changing it to this: ```python class testlibrary: @keyword("Testing embedded ${arguments}") def test_embedded_arguments(self, arguments:...

You could simply use `do_stuff(self, things)` or, if you want to preserve type hints, `do_stuff(self, things: CustomObject | list[CustomObject])`. In both cases you'd then need to check inside the keyword...

:+1: for just one standard and one web site. Based on a quick look there aren't any real differences except to the extension (.`jsonl` vs `.ndjson`). Having a common extension...

The owner of the ndjson domain seems to be fine [going forward with jsonlines.org](https://github.com/ndjson/ndjson-spec/issues/35#issuecomment-1285673417).

Could you please clarify what is the problem?

PR #64 covers this.

This problem has been reported and already fixed in 2020 (#58) but there hasn't been any release after that. A bug fix release with this and other Python compatibility fixes...

Closing this as a duplicate of #58.