-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payment method auto-capture boolean provides 3 options to the user #3697
Comments
@seand7565 hmm, not sure this is an actual issue. The first option corresponds to |
@aldesantis Right, behind the scenes the value is either (I prefer the first option, but maybe that's just me) No problem with the logic, just nitpicking at the text in the provided options. 😛 |
Ah, sorry, didn't realize you were referring to the label! I think the best option is to use yes/no consistently, since true/false only makes sense for developers. |
Yeah, for consistency I think the ideal options are probably:
|
I believe I fixed this in #3703 according to the consensus here.
However, I wonder if it would be better to remove the redundant option from the dropdown to reduce cognitive overhead. While having the third option makes sense to the store's developer, it could be confusing to users. Why have three answers to a yes or no question? The user may wonder if there is any difference between "Use App Default (No)" and "No"—At least, I wondered this when first setting up payment methods. So, my pull request as submitted makes the verbiage more consistent. That said, I could update it if others agree that reducing it to just two options is preferable, as in:
To take it one step further, I think something like the following would be easiest to scan and parse:
|
@michaelmichael when you select "Use App Default", what happens under the hood is that the value of the preference will be set to |
@aldesantis Makes perfect sense 👍 |
Yep, that covers it! Thanks so much @michaelmichael |
The value of auto-capture is a boolean, but has three possible values in the following image:
false
,yes
, andno
.IMO we should use
true
andfalse
instead ofyes
andno
, but we could also set the value of app default toyes
andno
- as long as we're consistent with our options.The text was updated successfully, but these errors were encountered: