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

In plaint text files | alone should be considered empty line in pipe-separated format #1816

Closed
boakley opened this issue Oct 6, 2014 · 1 comment
Assignees
Milestone

Comments

@boakley
Copy link

boakley commented Oct 6, 2014

In pipe-separated files, if I have a single pipe in a Settings table I get the error "Non-existing setting '|'". I think instead, robot should just ignore the line.

Run this test suite to get the error:

*** Settings ***
| Suite Setup | Log | In suite setup...
|

*** Test Cases ***
| Hello
| | log | hello, world

I would like to be able to have (mostly-)blank lines in settings tables, but robot throws the error "Non-existing setting '|'

The error goes away if I leave the line completely blank, but I would like to have the option of keeping the vertical pipe there, because I think it makes the test easier to read. In this contrived example it doesn't really matter, but in real world tests I like to separate my libraries and resource files from other settings, and the vertical bar makes it all visually appear as a single table rather than two tables separated by a blank line, eg:

*** Settings ***
| Resource | ...
| Resource | ...
| Library  | ...
| Library  | ...
| Library  | ...
| 
| Suite Setup | ...
| Suite Teardown | ...
@pekkaklarck pekkaklarck self-assigned this Oct 6, 2014
@pekkaklarck pekkaklarck added this to the 2.8.6 milestone Oct 6, 2014
@pekkaklarck pekkaklarck changed the title erroneous error "Non-existing setting '|'" in pipe-delimited file In plaint text files | alone should be considered empty line in pipe-separated format Oct 6, 2014
@pekkaklarck
Copy link
Member

Fair enough. You get similar problems also if using pipes alone elsewhere than in the setting table.

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

2 participants