Pekka Klärck

This is due to #5000. The motivation of that enhancement was making it more convenient for listeners and model modifiers to set keyword arguments, and it didn't occur to me...

This problem can be reproduced also without a library by passing keyword name and arguments as a list variable to `Run Keyword` so that it needs to resolve also arguments:...

We discussed about this on Slack some time ago and made a decision to revert the change done in #5000 in RF 7.0.1. Development of that release has been stalled...

RF 7.0.1 rc 1 with this fix [has just been released](https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-7.0.1rc1.rst). It would be great if you could test does the fix work properly before the final release that's targeted...

We could easily enhance `Should Contain` so that if the container (i.e. the first argument) is bytes and the item to check (i.e. the second argument) is a string, we...

Based on the discussion on Slack, the above problem occurs because DataDriver has already taken the functionality introduced in #5000 into use. That functionality has now been reverted as part...

The new, temporary API for creating named arguments with non-string values has been added. There exists new `robot.running.model.Argument` class accepting `name` and `value`, that can be used in `robot.running.model.Keyword.args`. `Argument`...

The new approach worked with DataDriver and also with OpenApiDriver. Thanks for testing @Snooz82 and @robinmackaij!

Thanks for the PR @droeland. It looks pretty good, but there are some smallish things that could be still enhanced. See the PR review for more details.

Are you @droeland planning to fix the small issues I mentioned in the PR review? If you don't have time, I can do that myself as well. I'm now more...