You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently keywords and control structures are formatted differently in the log file than they look in the data. For example, you have a keyword call like
Log Many a b c
and a FOR loop like
FOR ${x} IN cat dog horse
in the data, they look like
KEYWORD BuiltIn.Log Many a, b, c
and
FOR ${x} IN [ cat | dog | horse ]
in the log file.
I believe this should be changed. Most importantly, we should use the normal four space separator between items and omit all markers that wouldn't be supported in the data. The above examples could look like
KEYWORD BuiltIn.Log Many a b c
and
FOR ${x} IN cat dog horse
The text was updated successfully, but these errors were encountered:
This was broken recently in a refactor so that RETURN value was shows
a string representation of a tuple. Before that values were joined
together with a comma. After this fix the separator is four spaces to
be in line with #4900.
Currently keywords and control structures are formatted differently in the log file than they look in the data. For example, you have a keyword call like
and a FOR loop like
in the data, they look like
and
in the log file.
I believe this should be changed. Most importantly, we should use the normal four space separator between items and omit all markers that wouldn't be supported in the data. The above examples could look like
and
The text was updated successfully, but these errors were encountered: