- Issue created by @kay64
- last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - last update
9 months ago 30,139 pass, 1 fail - last update
9 months ago 30,141 pass, 2 fail - last update
9 months ago 30,141 pass, 2 fail - @kksandr opened merge request.
- last update
9 months ago 30,146 pass - Status changed to Needs review
9 months ago 3:47pm 10 September 2023 - Status changed to RTBC
9 months ago 2:33pm 12 September 2023 - 🇺🇸United States smustgrave
Thank you for including test-only patch.
Only question would be the todo linking to follow up issues but will see if committers think that's an issue.
LGTM
- last update
9 months ago 30,148 pass - last update
9 months ago 30,154 pass - last update
9 months ago 30,161 pass - last update
9 months ago 30,164 pass - last update
9 months ago 30,168 pass - last update
9 months ago 30,205 pass - last update
9 months ago 30,205 pass - last update
9 months ago 30,360 pass 6:34 2:21 Running- last update
9 months ago 30,360 pass - last update
9 months ago 30,371 pass - last update
9 months ago 30,379 pass - last update
9 months ago 30,377 pass - Status changed to Needs work
8 months ago 5:07am 9 October 2023 - 🇳🇿New Zealand quietone New Zealand
@kksandr, thanks for issue and the MR!
I'm triaging RTBC issues → . I read the IS, which is missing several sections. I have restored those in case they are needed and so we have the 'remaining tasks' section. I read the one comment that gives thanks for the test only path and leaves a question for the committer team. I do not see evidence of a code review.
I applied the diff and read the comment with the @todo. The comment should be wrapped correctly and instead of referring to a file it should refer to a class, or method. That said, I then ran the test without the added user to see the failure. That was at
/var/www/html/core/lib/Drupal/Core/ParamConverter/EntityConverter.php:149
which also has a todo. And that todo refers to https://www.drupal.org/node/2934192 → which is removing the block of code where the test is failing. It seems to me the @todo should point to that issue. Unless, I am missing something. Then, when that is fixed the creation of the user can be removed. (I tried that by applying that patch and removing the creation of the user and the test passed). Also, the anonymous user should only be created in the test where it is needed, instead instead of in the setup.In testLabelFormatter, the value
build[0]['#url']
is always unset. Surely, there should be a test for when it is set.Setting to needs work for the above.