- 🇬🇧United Kingdom catch
I think this could use an evaluation of which (if any) of these fields types are in use, or planned to be in use, in Drupal CMS. If they are, and they're otherwise high usage, then we could look at including them in core, but feels unlikely otherwise. There was also a discussion recently in slack, not sure there's an issue yet, about telephone really belongs in core, because a lot of sites have to install one or two contrib modules to make it usable.
- 🇦🇺Australia pameeela
I personally have never used the Currency or Country field and their usage is quite low. Address is included in the event recipe, and would be for other relevant recipes. I would be open to the argument that we should ship Address by default, but is there a case for the other two?
- 🇬🇧United Kingdom catch
I've also never used the country or currency fields.
For me personally I would leave the address dependency to specific recipes (and pretty much the same with any other module that's not directly supporting base recipes), because if it's not installed, it can cause composer dependency issues down the line.
- 🇦🇺Australia pameeela
OK, that aligns with our general approach to only add modules we actively need rather than adding ones that may come in handy.