Pekka Klärck

When discussing about tagging on Slack, @Snooz82 proposed adding `Keyword Tags` to make it easier to specify common tags for all keywords in a resource file. I think that's a...

In this comment I'll explain the current proposals related to changing tag related settings, what I think should be the end goal, and what would be the first steps towards...

Could you clarify what these instructions should contain?

:+1: for `robot:remove`, `robot:flatten` and `robot:expand`. Not showing `robot:*` tags in Libdoc HTML output is probably a good idea as well (but they should be included in spec files). These...

`robot:expand` would probably be pretty trivial to implement because we only needed to hook it up with the current `--expandkeywords` functionality (#2698). Could definitely be included in RF 5.1. Not...

I also agree that using `robot:flatten` with all keywords in a resource file would be a good use case for the new `Keyword Tags` setting (#4373).

Extending the existing flattening functionality probably isn't a good idea. It works by omitting certain elements when parsing output.xml. A better solution would be not writing those elements into output.xml...

A nice thing with flattening is that messages are preserved so debugging problems shouldn't be more complicated than normally. Not needing to expand various keywords could even make it easier....

Exposing argument conversion publicly would be a good idea. Not exactly sure what's the best API for that, though. Anyway, something that could be added in RF 5.0.

Could you @aaltat clarify this request a bit more? I checked the linked Browser library issue and notice it was fixed already. Was this issue not relevant or was there...