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

cucumber-expressions: returns undefined instead of empty string #746

Closed
charlierudolph opened this issue Oct 10, 2019 · 0 comments · Fixed by #754
Closed

cucumber-expressions: returns undefined instead of empty string #746

charlierudolph opened this issue Oct 10, 2019 · 0 comments · Fixed by #754

Comments

@charlierudolph
Copy link
Member

charlierudolph commented Oct 10, 2019

Summary

Reported in cucumber/cucumber-js#1241 that a cucumber-expressions of the form 'string {string} equals {string}' when matched against Given string "" equals "" returns undefined for the string values instead of empty strings.

Expected Behavior

When matching the cucumber-expression 'string {string} equals {string}' against the text Given string "" equals "", the values parsed should be empty strings.

Current Behavior

When matching the cucumber-expression 'string {string} equals {string}' against the text Given string "" equals "", the values parsed are each undefined.

Possible Solution

Not sure what changed but was working fine in previous versions. Its still matching correctly but for some reason isn't extracting a value

Steps to Reproduce (for bugs)

  1. Linked to repo to reproduce: https://github.com/jbblanchet/cucumber-error
  2. Clone repo
  3. npm install
  4. ./node_modules/.bin/cucumber-js

Context & Motivation

Your Environment

  • Version used:
  • Operating System and version:
  • Link to your project:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants