Livio Spring 0f6380b474 fix: use a single translator for middleware (#10633) ...

# Which Problems Are Solved

Comparing the v3 and v4 deployments we noticed an increase in memory
usage. A first analysis revealed that it might be related to the
(multiple) initialization of the `i18n.Translator`, partially related

# How the Problems Are Solved

Initialize the tranlator once (apart from the translator interceptor,
which uses context / request specific information) and pass it to all
necessary middleware.

# Additional Changes

Removed unnecessary error return parameter from the translator
initialization.

# Additional Context

- noticed internally
- backport to v4.x

(cherry picked from commit a0c3ccecf7)

2025-09-15 08:30:05 +02:00

..

bundle.go

fix: use a single translator for middleware (#10633)

2025-09-15 08:30:05 +02:00

fs.go

fix(middleware): init translation messages (#7778)

2024-04-16 15:46:13 +02:00

languages.go

feat: restrict languages (#6931)

2023-12-05 11:12:01 +00:00

translator.go

fix: use a single translator for middleware (#10633)

2025-09-15 08:30:05 +02:00