-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Feature]: Changing the flag to US flag in currency widget's default option #22167
Comments
@Rishabhkaul congrats on opening your first issue :) |
We have multiple conflict around this, specially the US - types (even comes up with country codes), here is a similar issue #18136 @dilippitchika did document the way forward here |
@somangshu let's kill the country flag in the currency widget, it serves no purpose, the final output is just a currency irrespective of where it's used. Phone is slightly different |
@dilippitchika can you frame what the final option needs to look like, we will modify our object accordingly! |
@dilippitchika makes sense, so for the currency thing we will do While we are thinking about this, Should we also rectify the problem with country code in phone input widget? #18136 |
We can try it out in phone input but there we need to write the countries because +1 or +2 on it's own is not clear to users. So we have to mention all countries either in short code or full name in the field. But that's a ux issue. |
Hey! Is anyone working on this issue? Or is anyone open to collaborating? |
Thanks for showing interest on the issue @Vishrut19, We would like to manage this issue internally. |
Is there an existing issue for this?
Summary
The default option when using the currency widget is a lesser known flag corresponding to USD. It should probably be US flag. This is on Appsmith cloud.
Why should this be worked on?
US $ is a reasonable default to have in the currency input. However it makes sense to put the US flag there, instead of the current option (I don't know what country that is) since for most cases where people will use US $, they're probably based in USA.
I'd also imagine it might be a relatively minor fix.
The text was updated successfully, but these errors were encountered: