Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make keywords and control structures in log look more like original data #4900

Closed
pekkaklarck opened this issue Oct 13, 2023 · 0 comments
Closed

Comments

@pekkaklarck
Copy link
Member

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
@pekkaklarck pekkaklarck added this to the v7.0 milestone Oct 13, 2023
@pekkaklarck pekkaklarck self-assigned this Oct 13, 2023
pekkaklarck added a commit that referenced this issue Oct 18, 2023
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant