Good point. We already have a similar capabilty for currency (default unit) so whoever implements this can take inspiration from it.

We should also consider adding it for phones (but for phone we should be able to leave it as blank / with no default country, like today)

https://www.figma.com/design/xt8O9mFeLl46C5InWwoMrN/Twenty?node-id=34845-128087&node-type=frame&t=WdI3ZY5Lsc7ylyqB-11

@Bonapara looks good!

Can you assign this to me?

Sure @sreyas-b-anand, thanks for contributing!

I see that the previous contributor was removed, would you be able to assign this to me? @Bonapara

Sure @sri-c9 , thanks for contributing!

sorry i thought this was nextjs not nestjs

Question to @Bonapara :

• I cannot remove a country today. It should be an option for the users ?

• If I start from an empty address, and I click only to open the INPUT without filling anything. If we prefill the country by default, should it save automatically when I click outside ? or not ?

ping @FelixMalfait @charlesBochet

@guillim great point, we can add a "No country" value in the dropdown

https://www.figma.com/design/xt8O9mFeLl46C5InWwoMrN/Twenty?node-id=24182-600671&node-type=instance&t=DtzuFw1XVhAUBGqX-11

@guillim I checked after our conversation and the default currency is actually set on the frontend when editing a currency field. Which means it's set to null by default but if you open/close the input then it'll be set to your default value. We don't really feel it on the currency field because there's also an additional condition so that we shouldn't display anything unless the amount is not null.
I think that behavior is fine and we could have the same behavior on phone numbers (also hiding the number if only the country has been recorded).

For the address field type it's slightly more annoying because if we open/close the address field and it has a default value, then the country will become visible in read-only mode because we don't require setting an address to display it.
I don't think it's a big issue because:

• the user can always set the value back to null manually since you'll introduce that option
• in the future, we will likely introduce additional settings on the address field later to allow the user adjust the address display format.
• in the future, there will be other evolutions to the address field which could impact the decision (e.g. add Google Maps auto-complete)

Overall I don't think it's worth overthinking this feature. We should go with whatever makes more sense for you.

Hi @Bonapara! I am currently working in a group of 5 students from CMU taking an introductory software engineering course and our final project is to contribute to an open-source repo. Our project has multiple checkpoints and will be due on December 8 (meaning our PR will take longer to open). Would it be possible for us to be assigned to this issue (or any issues that you think would be a good fit)? Thanks!

Sorry @JorgeGraciaViveros, @guillim is already on it

Technical consideration:

The default value already exist in the Metadata object. Therefore it's better to use it instead of the Settings field.

TODO items (#8614 )

• Address country backend validator
• Address country backend test
• Phone country backend
• Address preview country update (front)
  Viewed with @Bonapara , we only update the country, not the number and the street.
  So 456 Oak Street, Unit 3B, Springfield, United States would become 456 Oak Street, Unit 3B, Springfield, India. We do not make it reactive, waiting for Preview : Inline Settings not reactive #8556 for that
• Address CountrySelect component (front)
• Address Country Form component (front)
• Phone Country Form component (front)
• Make sure using the functions stripSimpleQuotesFromString and its alter-ego