The idea is:
The Form Trigger allows default values by using query parameters. But very often in a multistep form we also need to prepopulate values. Right now the node provides a “placeholder” that is grayed out and cannot be copy/pasted and disappears when the user adds any input. What’s missing is another field for “default value”.
My use case:
I have a multistep form where I enable class administrators to edit the title and subtitle of a class.
Step 1 executes a postgres query to get the list of classes. The next step is a dropdown that is dynamically populated with the list of classes. The class Admin chooses which class they want to modify.
The issue comes up on the third page: I give them fields where they can enter the new Title and the new Subtitle. Usually those are small changes from the existing values, so I want to prefill those fields with the existing values and let them make subtle edits. But I have no way to do that. Using a placeholder is actually confusing and frustrating UX.
I think it would be beneficial to add this because:
There are a lot of cases where multistep forms are used to modify existing data. Prefilling fields has lots of possible applications.
Ideally this capability would be added to fields of type date, text, email, textarea, and number. It probably should NOT be added to field type password.
Any resources to support this?
None needed
Are you willing to work on this?
Willing yes, able no. Nobody wants me working on code that someone else will use in production.