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

Tag search does not handle spaces in query #2736

Open
JFoederer opened this issue Mar 25, 2024 · 2 comments
Open

Tag search does not handle spaces in query #2736

JFoederer opened this issue Mar 25, 2024 · 2 comments
Labels
pending Pending of response from creator or other parts prio-low Nice to haves, if we have time and aren't working on something else
Milestone

Comments

@JFoederer
Copy link
Collaborator

Using the Tag search dialog I am able to find tests tagged with TAG_A (underscore), but not the ones tagged with TAG B (space), when searching using the full tag name (Results: 0). It does work when using a wild card search TAG*B.
image

v2.1dev22, Windows Python 3.11 and Linux Python 3.10

@HelioGuilherme66 HelioGuilherme66 added prio-low Nice to haves, if we have time and aren't working on something else bug Malfunctions that should be fixed to comply with the expected behavior labels Mar 25, 2024
@HelioGuilherme66 HelioGuilherme66 added this to the v2.1 milestone Apr 4, 2024
@HelioGuilherme66
Copy link
Member

@JFoederer The reason why the tags with spaces are not found, is because the space is the separator in the search field.
You want to search for Test B but you are searching for Test or B.
I tend to leave this as it is because it is similar of how we do in command line, we have to use theTest_B or TestB.

@HelioGuilherme66 HelioGuilherme66 added pending Pending of response from creator or other parts and removed bug Malfunctions that should be fixed to comply with the expected behavior labels Apr 7, 2024
@JFoederer
Copy link
Collaborator Author

Ok, I had not guessed that TAG_B and tagB were also valid to match TAG B. I understand that command line has this limitation as it doesn't deal well with spaces in general. In Robot Framework spaces are very common in names, so I would expect a dedicated RF tool like RIDE to work equally well with such names.

But, if this was intended behaviour than it isn't a bug and with three workarounds available it certainly isn't a high prio feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending Pending of response from creator or other parts prio-low Nice to haves, if we have time and aren't working on something else
Projects
None yet
Development

No branches or pull requests

2 participants