-
Notifications
You must be signed in to change notification settings - Fork 16
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
Bugs in regular expression matching #39
Comments
OK. Let me have a look. |
vincent-zurczak
added a commit
that referenced
this issue
Sep 29, 2023
Sorry for the delay. Thank you for reporting these issues. :) |
vincent-zurczak
added a commit
that referenced
this issue
Oct 12, 2023
#39 Support spaces and dashes in regular expressions
I have just merged and tagged a new version (1.2.1). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
I upgraded to the latest release (1.2.0) to get the new regular expression matching feature (thanks also for the additional documentation!).
Unfortunately, I encountered two limitations:
It is not possible to use an expression like
try "at most 5 times every 5s to get Route named '${ROUTE_NAME}' and verify that '.spec.tls.certificate' matches 'BEGIN CERTIFICATE'"
.Given this input:
This line of code fails:
bats-detik/lib/detik.bash
Line 266 in 7927bb1
and only keeps
-----BEGIN
invalue
(instead of the entire line).It is not possible to use an expression like
try "at most 5 times every 5s to get Route named '${ROUTE_NAME}' and verify that '.spec.tls.certificate' matches '----END CERTIFICATE----$'"
, because the leading dashes get interpreted as an argument for bash.The text was updated successfully, but these errors were encountered: