Error: Cannot use object of type Drupal\Core\StringTranslation\TranslatableMarkup as array

Also as patch, next to the MR.

Thanks for reporting

Changes will need to be in an MR against 11.x

Also will need a test case showing the bug.

I will create a MR for #3 patch.

I already can see the changes in the in the branch.

Hey all
I've added a test scenario let me know if that makes sense
any reviews are welcome :D https://git.drupalcode.org/project/drupal/-/merge_requests/12390

Appears to have a pipeline issue

I'm sorry but I'll need to give up this one, I'm out of ideas on how to solve the test problems that I'm facing

Hello
I am assigning it to myself for trying to resolve the test problems thanks

Hello @julio_rekwa,
It seems the branch you're using might not be aligned with the expected naming convention. Ideally, it should be something like:
git checkout 3526541-error-cannot-use However, your MR branch appears to be: issue/drupal-3526541:11.x

When I check out this branch (issue/drupal-3526541:11.x), I do see all the changes from the MR, but Git shows the state as:
HEAD detached at drupal-3526541/11.x

This typically indicates that the branch is tracking a remote ref directly without creating a local branch. Let me know if this is intentional or if we should align on a consistent branch naming and checkout approach.

Also, attaching a patch file, please check if it is resolving the pipeline issue.
2025-06-24/3526541-error-cannot-use.patch
Thanks.

oily → changed the visibility of the branch 11.x to hidden.

@julioretkwa I am trying to get the pipeline to show green with a minor PHPSTAN fix. Your test coverage in your new branch can be ported over to the active branch, then. Then can make sure the test works correctly in the pipeline, too.

RE: #14 Trying a merge request to see if the active fork/ MR is syncing with the 11.x dev branch. It is currently about 90 commits behind it.

@julio_retkwa If you want to have another go at the test coverage, good if you can start by merging your test into the active branch. Can then run manually the 'test-only' test which will fail if test coverage is working well.