{"action":"created","issue":{"url":"https://api.github.com/repos/cucumber/cucumber/issues/317","repository_url":"https://api.github.com/repos/cucumber/cucumber","labels_url":"https://api.github.com/repos/cucumber/cucumber/issues/317/labels{/name}","comments_url":"https://api.github.com/repos/cucumber/cucumber/issues/317/comments","events_url":"https://api.github.com/repos/cucumber/cucumber/issues/317/events","html_url":"https://github.com/cucumber/cucumber/issues/317","id":282313032,"number":317,"title":"cucumber-expressions: non capturing group wildcard parameter type","user":{"login":"mikehaas763","id":2096573,"avatar_url":"https://avatars1.githubusercontent.com/u/2096573?v=4","gravatar_id":"","url":"https://api.github.com/users/mikehaas763","html_url":"https://github.com/mikehaas763","followers_url":"https://api.github.com/users/mikehaas763/followers","following_url":"https://api.github.com/users/mikehaas763/following{/other_user}","gists_url":"https://api.github.com/users/mikehaas763/gists{/gist_id}","starred_url":"https://api.github.com/users/mikehaas763/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikehaas763/subscriptions","organizations_url":"https://api.github.com/users/mikehaas763/orgs","repos_url":"https://api.github.com/users/mikehaas763/repos","events_url":"https://api.github.com/users/mikehaas763/events{/privacy}","received_events_url":"https://api.github.com/users/mikehaas763/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-12-15T03:55:55Z","updated_at":"2017-12-15T18:53:48Z","closed_at":null,"author_association":"NONE","body":"I'm using cucumber-js, not sure if this applies to all cucumbers.\r\n\r\nMaybe I'm missing this in the docs (https://docs.cucumber.io/cucumber-expressions/#) and can already do this as is. I'd like to use the new CucumberExpression syntax to match any characters, but not be required to add a parameter to the function for the group.\r\n\r\nI'm pretty sure I could do this with my own custom `ParameterType` but I think it would be valuable to others if it was baked in. Maybe something like `{*}`?"},"comment":{"url":"https://api.github.com/repos/cucumber/cucumber/issues/comments/352083544","html_url":"https://github.com/cucumber/cucumber/issues/317#issuecomment-352083544","issue_url":"https://api.github.com/repos/cucumber/cucumber/issues/317","id":352083544,"user":{"login":"mikehaas763","id":2096573,"avatar_url":"https://avatars1.githubusercontent.com/u/2096573?v=4","gravatar_id":"","url":"https://api.github.com/users/mikehaas763","html_url":"https://github.com/mikehaas763","followers_url":"https://api.github.com/users/mikehaas763/followers","following_url":"https://api.github.com/users/mikehaas763/following{/other_user}","gists_url":"https://api.github.com/users/mikehaas763/gists{/gist_id}","starred_url":"https://api.github.com/users/mikehaas763/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikehaas763/subscriptions","organizations_url":"https://api.github.com/users/mikehaas763/orgs","repos_url":"https://api.github.com/users/mikehaas763/repos","events_url":"https://api.github.com/users/mikehaas763/events{/privacy}","received_events_url":"https://api.github.com/users/mikehaas763/received_events","type":"User","site_admin":false},"created_at":"2017-12-15T18:53:48Z","updated_at":"2017-12-15T18:53:48Z","author_association":"NONE","body":"Our POs like to use natural language like `Given a *product* user` ... where *product* is not a finite set. Could be 1-3 words. If relevant, our gherkin is sometimes influenced by the fact that we're at the start of our BDD journey. We're currently bound to many mainframes and many layers of APIs that we can't control, and so we don't have any way to programmatically stage data. We have to manually stage user data in a persistent store ahead of time. I'm all ears if you think we should be doing something different, I just think a wildcard could be useful for companies like mine that are at the beginning of their journey."}}
{"actor":{"display_login":"mikehaas763"}}