Deprecate comment libraries and move to history module

Created on 22 August 2025, about 1 month ago

Problem/Motivation

Part of πŸ“Œ Remove uage of history module from comment module Active

Steps to reproduce

Proposed resolution

Move comment/drupal.comment-new-indicator and comment/drupal.node-new-comments-link libraries to history module.

Deprecate the old libraries.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component

history.module

Created by

πŸ‡¦πŸ‡ΊAustralia mstrelan

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @mstrelan
  • Merge request !13059Move libraries β†’ (Closed) created by mstrelan
  • Pipeline finished with Success
    about 1 month ago
    Total: 622s
    #578882
  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    We could possibly move the usage of these to history.module at the same time, it's a bit odd the way it is, but potentially makes it easier to review.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Could we go ahead and move it? MR is line change is pretty manageable so adding more won't be difficult. Just seems goal is to untangle history from comment.

  • Pipeline finished with Failed
    about 1 month ago
    #580489
  • Pipeline finished with Failed
    about 1 month ago
    #580498
  • Pipeline finished with Canceled
    about 1 month ago
    #580511
  • Pipeline finished with Failed
    about 1 month ago
    #580512
  • Pipeline finished with Failed
    about 1 month ago
    #580515
  • Pipeline finished with Running
    about 1 month ago
    #580540
  • Pipeline finished with Failed
    about 1 month ago
    #580566
  • πŸ‡¦πŸ‡ΊAustralia mstrelan

    Ok I've moved everywhere the libraries were attached, and associated code. This makes a much larger diff stat, but it has to be either piecemeal like before or all together. A lot of the larger diff stat is for the duplicated test for the decorated service. Can't really avoid that either without losing test coverage. Could probably refactor the tests a bit but not much point since it's moving to contrib and it's easier to review if it doesn't change.

  • Pipeline finished with Success
    about 1 month ago
    #580567
  • The 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.

  • Pipeline finished with Success
    about 1 month ago
    Total: 692s
    #587602
  • Pipeline finished with Failed
    about 1 month ago
    Total: 753s
    #587609
  • Pipeline finished with Failed
    about 1 month ago
    Total: 761s
    #587613
  • Pipeline finished with Success
    about 1 month ago
    Total: 864s
    #587622
  • The 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.

  • πŸ‡ΊπŸ‡ΈUnited States nicxvan

    Took a quick look, looks mostly right. Another test conflict likely from the attribute conversion.

  • Pipeline finished with Failed
    22 days ago
    Total: 185s
    #595595
  • Pipeline finished with Success
    22 days ago
    Total: 685s
    #595599
  • Pipeline finished with Success
    16 days ago
    Total: 1008s
    #600633
Production build 0.71.5 2024