You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run behat --tags="" then I expect no exceptions to be thrown. In the version of behat that I'm running (3.8.1), it throws the following exception:
$ behat --tags="" --list-scenarios
In TagFilter.php line 146:
Warning: Uninitialized string offset 0
It looks like TagFilter doesn't check for the empty string before exploding the string and attempting to use array access on it.
The text was updated successfully, but these errors were encountered:
magikid
added a commit
to magikid/Gherkin
that referenced
this issue
Apr 26, 2022
If the `filterString` in `TagFilter` is an empty string, an exception
was being thrown because the code was expecting a non-empty string.
This checks if the string is non-empty and returns early if it is.
Issue: Behat#250
magikid
added a commit
to magikid/Gherkin
that referenced
this issue
Apr 26, 2022
If the `filterString` in `TagFilter` is an empty string, an exception
was being thrown because the code was expecting a non-empty string.
This checks if the string is non-empty and returns early if it is.
Issue: Behat#250
* Check for empty Tag filter string
If the `filterString` in `TagFilter` is an empty string, an exception
was being thrown because the code was expecting a non-empty string.
This checks if the string is non-empty and returns early if it is.
Issue: #250
* Use strlen instead of mb_strlen
strlen is O(1) and mb_strlen is O(n).
When I run
behat --tags=""
then I expect no exceptions to be thrown. In the version of behat that I'm running (3.8.1), it throws the following exception:It looks like
TagFilter
doesn't check for the empty string before exploding the string and attempting to use array access on it.The text was updated successfully, but these errors were encountered: