Default value for a Checkout UI settings field

Extensions
1

In addition to this thread, can i ask for feature request to add this functionality?

I am currently working with Checkout UI Extensions and have noticed that the shopify.extension.toml file does not support a default_value property for extensions.settings.fields.

Allowing these fields to be pre-filled ensures the Checkout Editor UI stays in sync with the extension’s behavior. Merchants can immediately see what the default is and modify it if needed, rather than looking at an empty field while the component renders a hardcoded string.

2

Just to make sure, default value of boolean is false?

3

Hi @Tomer_Klein,

Thanks for sharing your feedback with us!
You make an excellent case about communicating the default value of settings to merchants.
I’ll put this down in our list of requests, and we’ll provide an update here if and when we implement this.

Also yes, default of the boolean setting is false.

1 Like
4

Thanks for your reply, I really appreciate you considering this request.

This is directly related to an extension we’re currently about to release, and I wanted to share that working with empty default values in the settings has proven to be quite unintuitive and surprisingly challenging, both for us as developers and for merchants during setup.

If there is any way to prioritize or further escalate this request, it would make a meaningful difference for real production apps like ours.

Thanks again for taking the time to consider it, much appreciated!

1 Like
5

We look at both how useful the functionality would be and how much demand there is for it. Right now, we understand it can lead to an unintuitive user experience that’s difficult to work with, which already makes this request a higher priority for us. If others chime in with the same request, that will still help us better gauge demand and prioritize it accordingly.

1 Like