-
Notifications
You must be signed in to change notification settings - Fork 19
IBX-10215: Fixed SourceLanguageValueResolver
argument's name
#1612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Care to elaborate? It's not that obvious at first glance.
TargetLanguageValueResolver
argument's nameSourceLanguageValueResolver
argument's name
I updated the description |
SourceLanguageValueResolver
argument's nameSourceLanguageValueResolver
argument's name
a7203a4
to
ad4f98e
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked many places and found that the translation doesn't work in one specific section — Catalogs. It's the same issue as described in the task. I'm sending a video.
Nagranie.z.ekranu.2025-07-10.o.13.18.36.mov
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA Approved
Regression: ibexa/commerce#1390 (the regression fails isn't related to these PRs.)
Related:
https://github.com/ibexa/product-catalog/pull/1364
Description:
Fix to the obvious typo : )
Almost every 'update' controller action has the following param:
baseLanguage
, i.e.: https://github.com/ibexa/admin-ui/blob/main/src/bundle/Controller/ContentTypeController.php#L472 which is in fact resolved inSourceLanguageValueResolver
-> the argument name cannot be the same as inTargetLanguageValueResolver
.For QA:
Documentation: