Default currency symbol as setting or environment variable

[alexfacciorusso]

Is your feature request related to a problem? Please describe.
It is frustrating to have to change the currency symbol every time I create a field

Describe the solution you'd like
A field in the settings would be amazing, but if that's too complicated, an environment variable would be appreciated.

[alexfacciorusso]

This seems relatively simple to implement and I could give it a go

[kpodp0ra]

I propose saving the user's last selection in cookie/local storage. This way, the currency symbol can be automatically restored based on the user's previous choice, making the experience more seamless.

[tea-artist]

LLM's suggestion is good, so that the appropriate default currency symbol can be automatically selected on the front end.
And contributions are welcome.

Here's how you can get the currency symbol based on the user's locale:

// Get user's locale (e.g., 'en-US', 'de-DE', etc.)
const userLocale = navigator.language;

// Create a number formatter for currency using the user's locale
const formatter = new Intl.NumberFormat(userLocale, {
  style: 'currency',
  currency: 'USD' // You need to specify which currency you want to format
});

// Get the currency symbol
const currencySymbol = formatter.formatToParts(0).find(part => part.type === 'currency').value;
console.log(currencySymbol); // '$' for en-US, '€' for de-DE with EUR, etc.

A few important notes:

1. The currency symbol shown will be based on both the locale AND the currency code you specify
2. Some locales might show the currency code (like 'USD') instead of a symbol
3. The position of the symbol (before or after the number) will also be determined by the locale

You can also get the full formatted currency string:

const price = 42.99;
const formatted = formatter.format(price);
console.log(formatted); // '$42.99' for en-US

This is the recommended way to handle currency display as it respects the user's locale preferences and provides proper formatting for different regions.

[alexfacciorusso]

It's a fair suggestion although saving it as a cookie is almost thinking as a single-user system. If I set a default currency, I want to set it for all the team/at a space or base level! :)

[alexfacciorusso]

Maybe the priority table should be:

Base setting > Space setting > User locale > App default currency.

It doesn't have to be implemented altogether as a logic but can be split in steps/tasks, but that's what I believe can benefit the most

[kpodp0ra]

There is no need for base/space setting for default currency as currency is enforced on field-level. You only need to set currency when you are creating new table and in most use cases this isn't common task.