Skip to content

v2.0.2 — Laravel 11 container compatibility fix

Choose a tag to compare

View all tags
@BrunosCode BrunosCode released this 19 Mar 09:53
· 39 commits to main since this release
v2.0.2
7e297b6

Bug fix: setOption / setOptions overrides were silently ignored when resolving file and database handlers under Laravel 11.

What changed

TranslationHandlerService instantiates handlers by passing a TranslationOptions object to the Laravel service container:

// before
app($class, [$this->getOptions()]);

// after
app($class, ['options' => $this->getOptions()]);

Laravel 11 removed the automatic conversion of positional parameters to named ones (keyParametersByArgument). As a result, the container ignored the provided TranslationOptions instance and auto-resolved a fresh one from config — discarding any runtime overrides set via setOption() or setOptions().

Impact

Any option overridden at runtime was silently ignored. The most visible symptom was the CSV delimiter: selecting , in the import/export UI still used the default ; from config, causing:

Invalid CSV at line 2: expected at least 2 columns, got 1.
Check that the delimiter is ";"

The same issue affected all four handler factories (getPhpHandler, getCsvHandler, getJsonHandler, getDbHandler).

Affected versions

  • ^2.0 on Laravel 11 (which ships with Illuminate 11.x).
  • Laravel 10 was not affected because its container still supported positional parameter overrides.
Assets 2
Loading