Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
comment.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Sep 2025 at 01:55 UTC
Updated:
26 Mar 2026 at 14:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
mstrelan commentedComment #4
smustgrave commentedSorry to be that person
Did a quick search for CommentItemInterface::HIDDEN CommentItemInterface::OPEN and CommentItemInterface::CLOSED
found CommentItem::isEmpty (which also has OPEN and CLOSED)
Comment #5
mstrelan commentedNo need to apologise, thanks for finding that.
Comment #6
mstrelan commentedComment #7
smustgrave commentedAppeared to be the last reference
Comment #8
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #9
mstrelan commentedRebased and replicated changes from CommentLinkBuilderTest to the new HistoryCommentLinkBuilderTest
Comment #10
smustgrave commentedSeems like a good rebase
Comment #11
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #12
mstrelan commentedRebased and resolved conflicts due to #3513120: Fix LongLineDeclaration in Functional tests
Comment #13
astonvictor commentedIt works for me, but the only question: Should we use old names (HIDDEN, CLOSED, and OPEN - all uppercase)?
Comment #14
mstrelan commentedNo, this has already been through the coding style review process and we use PascalCase for enums.
Comment #15
astonvictor commentedok, thanks for the response
+1 RTBC
Comment #16
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #18
mstrelan commentedRebased, back to NR as I had to manually fix up some conflicts
Comment #19
smustgrave commentedSeems was previously RTBC before the bot
Comment #20
godotislateNW for merge conflict.
Comment #21
mstrelan commentedRebased. There was a conflict with comment_preview being moved from comment.module to CommentForm::preview so I reapplied one change there. The other conflict was because
core/modules/node/tests/src/Kernel/Migrate/d7/MigrateNodeTest.phpno longer exists.Comment #22
godotislateThis looks close.
Another merge conflict for added return type on
CommentTestTrait::addDefaultCommentField.Also MR suggestions to bump the deprecation version.
Comment #23
mstrelan commentedRebased, applied suggestions and updated the version in the CR.
Comment #27
godotislateCommitted 19163c5 and pushed to main and 3c48912 and pushed to 11.x. Thanks!
Made a small edit to the CR and published.
Comment #30
godotislateReverted 11.x for PHPStan errors. Needs a separate MR.
Comment #31
godotislateRe #30, looks like deprecation warnings
https://git.drupalcode.org/project/drupal/-/jobs/8860687
Comment #32
mstrelan commentedI think we should add those to the baseline for 11.x rather than fixing them, since those modules will be removed. I believe they were fixed in earlier iterations of the MR before removal.
Comment #33
godotislateThat sounds fine. Actually, I think the baseline can be downloaded from the failed job artifacts: https://git.drupalcode.org/project/drupal/-/jobs/8860687/artifacts/file/...
Comment #35
mstrelan commentedI opened an MR with the baseline added, but I'm not sure that'll work, I think the phpunit jobs might fail if the deprecations are still triggered. But I don't seem to have access to even view the failed job, so I can't really tell. I could put up another MR that fixes the deprecations in 11.x, but that would be updating modules that have already been split to contrib, so it seems weird.
Comment #36
godotislateStrangely I could not view the downstream job either, but I could re-run the parent job. So I did, and it passed.
Comment #37
mstrelan commentedOK great then I guess the 11.x MR needs review. It's a cherry pick of the commit to main, plus a regenerated baseline to ignore all the calls to deprecated constants from deprecated modules that have been split to contrib already.
Comment #38
smustgrave commentedSeems like a good backport.
Comment #40
godotislateCommitted 979d45e and pushed to 11.x. Thanks!