[Kadrian]

One source of truth for the currency: the frontend gets the ISO code of the parser currency, frontend.currency is gone.

Stacked on #4108. The old block (unit, separators, decimalScale) was shaped after a frontend library's props; both sides kept derived values of preprocessor.parsers.currency by hand, and the store read money with the frontend scale while the parser wrote it with the currency's fraction digits.

• /config/frontend sends currency: "EUR"; the frontend formats money with Intl in the app locale (history, preview, money range field) and derives symbol and decimals from the code
• backend reads scale and fraction digits from the parser currency everywhere: money filter values, MoneyIntStore, the arrow printer (no hard-coded 2)
• the API is unchanged: money filter values still go to the backend as integers in cents, arrow results still come back that way, so stored queries and saved form configs keep working
• config: frontend.currency is ignored when a deployment config still sets it (@JsonIgnoreProperties, review request), so configs can drop the block at their own pace
• downstream: package.json unchanged; its backend reads the old block in two places and gets the same one-line change with the submodule bump
• second commit: three pre-existing errors in openapi.yaml the linter now reports (unquoted NULL enum value, uniqueItems on items instead of the arrays); the file had not changed since 2024, so the lint job never ran on it

[Kadrian]

Hey @awildturtok this would be my proposal for how to simplify currency across backend & frontend, curious what you think!

[awildturtok]

Somit verhinderst du das crashen der neuen Instanzen und wir können vermeiden alle deployments direkt zu migrieren