Tyler Thompson

> we still have some cleanup to do as part of preparing for Swift 6 Great callout! I'll fiddle with a strict concurrency PR. I suspect this is mostly just...

Behavior is better, but failing tests and abandon does not appear to work anymore.

Him, I see this is marked completed and merged...however it's notable that when using Tuist 4.20.0 pointed at the example repository I included in this issue test targets are still...

> Hey @Tyler-Keith-Thompson 👋 > > What project exactly are you trying to generate? https://github.com/Tyler-Keith-Thompson/Afluent

My temporary workaround: ```Swift struct PrometheusClientKey: StorageKey { typealias Value = PrometheusClient } extension Application { var prometheusClient: PrometheusClient? { get { storage[PrometheusClientKey.self] } set { storage[PrometheusClientKey.self] = newValue }...

So I can certainly add step suggestions that make use of expressions. Could potentially even get clever and find a way to give both as an option. I'll add that...

Update: I've released a version that deprecates the string-based function. I'm gonna leave that for maybe a month and then I'll change behavior so that strings use expressions and regex...

Update: v4.0.5 removes the requirement to use "as CucumberExpression".

This seems like a totally fair ask...I'm slammed with work at the moment so I won't be able to turn this around super quickly. It certainly seems possible, cause test...

So for the generated step stubs I can totally add an XCTFail, that seems like a great addition. I'm hesitant to do more for a couple reasons. The first is...