Problem/Motivation

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.

Issue fork drupal_cms-3482992

Command icon Show commands

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

    phenaproxima created an issue. See original summary.

    johnwebdev’s picture

    +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 👍

    phenaproxima’s picture

    Title: The installer should collect input for recipes that need it » [PP-1] The installer should collect input for recipes that need it
    Status: Active » Postponed
    Related issues: +#3483435: Add a trait for forms that want to collect input on behalf of a recipe

    This 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

    phenaproxima’s picture

    Title: [PP-1] The installer should collect input for recipes that need it » The installer should collect input for recipes that need it
    Status: Postponed » Active

    The 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.

    phenaproxima’s picture

    Project: Drupal CMS development repository » Recipe Installer Kit
    Version: » 1.x-dev
    Component: Track: Installer » Code

    Moving to the Recipe Installer Kit project, which is where the runtime code for the installer (i.e., its business logic) will live.