Consider automatically adding RecipesForm as an install task if the profile lists any optional recipes

Created on 5 February 2025, 2 months ago

Right now, any optional recipe groups your profile defines will not be exposed to the user unless the profile specifically has RecipeForm in the forms array. That's the default, but it's a bit tricky. It might make sense to automatically put RecipeForm into the pre-database install tasks if the profile lists any optional recipe groups. I'm not sure, though; would this violate the principle of least surprise? Would it be good DX? Worth considering.

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @phenaproxima
  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    Ultimately, I think this probably makes sense.

    If you wanted to use your own recipe selection form, you'd be writing custom PHP, and you'd like alter the alterations made by Hooks::installTasksAlter() to do that.

    Making it as easy as possible to create recipe-based installers is the goal here, so I think this is a worthwhile feature.

Production build 0.71.5 2024