Skip to content

Swift Concurrency Support #47

Discussion options

You must be logged in to vote

Hrm, this is an interesting question. So I'll be clear, the library wasn't designed with async/await in mind at all. It'd be possible to add closures to steps that'd be async/await compatible, for that matter it'd be good if the existing closures would be updated to support throwing errors as well.

The design for this may take me a bit to nail down. I can't give you great advice on making this work right this second but I'll tell you that CucumberSwift steps execute synchronously, It might be possible for you to build something yourself that utilizes XCTWaiter() and an async closure to kind of hack in the functionality.

I'm happy to add it to the backlog of ideas, though. It's a totally r…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@fwpascual
Comment options

Answer selected by fwpascual
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants