Active
Project:
Recipe Installer Kit
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Oct 2024 at 19:36 UTC
Updated:
5 Feb 2025 at 03:02 UTC
Jump to comment: Most recent
It is possible for recipes to accept input, but there is no way for recipe input to be collected in the UI (yet). This can be a problem at install time if the user wants to apply recipes that need inputs (such as an API key).
Let's alter the installer so that it collects input on behalf of any selected recipes that want to ask for it.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
johnwebdev commented+1
I also think that accepting input should only be done when absolutely necessary otherwise go for good sensible defaults to not overwhelm the user 👍
Comment #3
phenaproximaThis is blocked by the necessary core API being added: #3483435: Add a trait for forms that want to collect input on behalf of a recipe
Comment #4
phenaproximaThe core API was added and is in Drupal 11.1.0-rc1, so this is no longer blocked. Having said that, we are not currently exposing any input-requiring recipes in the installer and I'm not sure we will for 1.0.0, so I don't think this is a stable blocker.
Comment #5
phenaproximaMoving to the Recipe Installer Kit project, which is where the runtime code for the installer (i.e., its business logic) will live.