Robotidy and pipe separators

94 views
Skip to first unread message

Geist Eng

unread,
Jul 29, 2022, 12:41:23 AM7/29/22
to robotframework-users
Just recently updated to Robot Framework 5.0 and trying to use the  external robotidy tool.

From a read of the docs I do not see support for adding pipe separators.  Testing shows robotidy can parse .robot files and removes the pipe separators as the Transformer for NormalizeSeparators states.

I suspect I will have to create an External transformer to get pipe separators back.  Is this correct, or am I missing something in the docs?

If so has anyone already created an External transformer to make a pipe separator?

Thanks.

Bartłomiej Hirsz

unread,
Aug 1, 2022, 5:01:31 AM8/1/22
to robotframework-users
Hi, 

I'm the author of the Robotidy. I missed your questions from this channel because (surprisingly) I wasn't there. But now I joined and I will try to answer your questions. 

We opted to not support pipes in Robotidy. Hovewer some people in the community wanted to support it and they added it through PR. To enable pipes you just need to configure --separator option (see --help for details). 
All our acceptance tests for transformers uses spaces. That's why it's possible that not all transformers work well with pipes - you can report any issue in our github issue tracker (https://github.com/MarketSquare/robotframework-tidy/issues) but pipes related issues will have lower priority. I can always take a look if it's something easy to fix /workaround though. 

Bartłomiej Hirsz

unread,
Aug 1, 2022, 5:01:31 AM8/1/22
to robotframework-users
Your question regarding external transformer is actually good idea though. Instead of trying to support pipes in every separate transformer (with --separator option set) we could add new non-default transformer that would replace all spaces to pipes at the end of the run. It would be more stable and easier to maintain (we would need tests just for this new transformer). I will think about this though it'll be lower priority.

piątek, 29 lipca 2022 o 06:41:23 UTC+2 Geist Eng napisał(a):
Reply all
Reply to author
Forward
0 new messages