Gáspár Nagy

@orifn1 Could you please share what `[StepArgumentTransformation]`s do you have in that project? It seems to be similar what @kaylumah reported at https://github.com/kaylumah/hosting/pull/552#issuecomment-1935668615

@orifn1 The ones with `string` return type might be the tricky ones. Can you temporarily comment these ones out and rerun (obviously the tests will fail, but hopefully not with...

> looks like this code is source of the problem How did you figure that out? (It might be relevant for the fix as well.)

@orifn1 thank you for looking into that. I didn't even remember that I made that comment. :) If you come up with any good workaround, please post it here.

No this is a regression in SpecFlow v3->v4 or in the Reqnroll porting (unfortunately I had to touch the converters, so it can happen that it was reintroduced during the...

If any of you could make a simple check with SpecFlow v4-beta to see if the regression was already present there, it would help the investigation.

@orifn1 thx. I will try to integrate this to the codebase next week.

@clrudolphi I think for other tags it works in general: [this test](https://github.com/reqnroll/Reqnroll/blob/main/Tests/Reqnroll.SystemTests/Generation/GenerationTestBase.cs#L230) verifies that for scenario outlines. So the only problem is with the `@ignore` tag (I think). For this...

@clrudolphi regarding my memories ignoring works in the following way: For scenarios the `@ignore` should be handled with attributes (`Skip="Ignored"` or `[Ignore]`), but if a scenario outline example set it...

@gasparnagy Answered as a review at the PR: I think this is good as it is.