Using [Required] with a HttpPolicy fails with FTL: Sequence contains no matching element

[carcer]

Describe the bug
Using [Requried] attribute with a custom HttpPolicy causes a FTL error

To Reproduce
Repo can be found here: https://github.com/carcer/wolverine/tree/broken_http_policy

Expected behavior
App should start

[LodewijkSioen]

I probably broke this use case with #1500 :(

[LodewijkSioen]

Your policy is added after the RequiredEntityPolicy so the middleware you add is not present in the list of middleware when RequiredEntityPolicy does its thing. Since there is nothing that creates the entity, this code will fail.

I see two solutions:

• Fallback to chain.Middleware.Add(stopFrame) if no middleware that produces the entity is found
• Instead of adding the null-check after the creating middleware, add it to the consuming middleware

Problem with the second solution is that there doesn't seem to be a way to determine the method parameters for a Frame in the middleware collection.

[carcer]

We have been ok with removing the attribute, so its not blocking us. Might be worth at a minumum improving the error handling here. It currently FATALS and created no real info to easily tell why it failed without diving into breakpoints in Wolverine

[LodewijkSioen]

@jeremydmiller could it be that this one dropped of your radar? My PR should fix the issue and make the whole more robust.