-
-
Notifications
You must be signed in to change notification settings - Fork 2k
CucumberDocStringException when using docstring with content type but no DocStringType defined #2458
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
Milestone
Comments
Looks like we're missing a fall back for String and DocString somewhere. |
mpkorstanje
added a commit
that referenced
this issue
Jan 6, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 6, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 7, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 7, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 7, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 7, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 7, 2022
mpkorstanje
added a commit
that referenced
this issue
Jan 7, 2022
Fixed in v7.2.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Upgrading to version 7.2.0/7.2.1 breaks some of our existing scenarios where a docstring with content type is used but no custom
DocStringType
is defined.To Reproduce
Scenario:
Glue code:
Error:
Expected behavior
I'm not sure if the usage we had until now was supposed to be working but it actually was, thus I would expect no change for a minor version upgrade.
Moreover I'd like to be able to define content type on docstring without having to explicitly define a
DocStringType
if the step is expecting aString
. Shouldn't there be a default converter toString
?Your Environment
The text was updated successfully, but these errors were encountered: