Recipes make a lot of sense when there are many ways of doing something and it is up to you to pick the right tool for your specific needs (for example, that PR has both a "results as state" model and "results as events" model - one size does not fit all use cases), but we're definitely looking at what recipes "graduate" to become optional helpers in the library itself over time. Then we'll rewrite the recipe to use the new helper - that way the nav3-recipes repository remains a good source for how to approach specific problems