Pekka Klärck

It turned out this issue is too badly backwards incompatible to be done already in RF 7.0. We need to first deprecate using arguments starting with `$` or other variable...

Could you clarify your worries? The change will affect usages like ``` Keyword $something ``` where the argument starts with one of `$@&%`. Using these characters inside arguments won't be...

I don't like a command line option too much, because it would effectively hide all warnings and errors. It's in general best to fix the reported issues instead. The log...

This is actually pretty complicated to do. The problem is that we in general want to deprecate usages like ``` Keyword $foo ``` but there are special case like ```...

The problem is that if someone nowadays uses ``` Keyword $xxx ``` so that `$xxx` is a literal value, the behavior will change and the usage needs to be changed...

There are two possibilities: - Add separate `Should Be Equal As Bytes` keyword. - Enhance `Should Be Equal` itself so that it accepts an optional argument specifying the expected type....

This would be a handy enhancement. Let's try to get it done already in RF 7.1.

We try to get RF 7.1 out soonish and I don't think we can fit this one in. I still think this is a handy enhancement and I move this...

The plan has been to get RF 7.1 out in July, but August is more realistic at this point. To get it out soonish, we have been thinking about RF...

It's strange that the resource isn't imported again if the variable used in the path changes. One possibility is that we use the original resource file path, without variables being...