Problem/Motivation

As discovered in #3123832: [META] Fix @todo items referencing closed issues, there is a @todo in \Drupal\comment\CommentManager which has a link to an issue that is closed as a duplicate.

Let's point that link to the issue that is still open.

Steps to reproduce

Proposed resolution

- The current @todo links to #1029708: History table for any entity
- That was closed as a duplicate of #2081585: [META] Modernize the History module, which is actually a [META] issue
- Of that [META] issue, #3267011: [PP1] Use the HistoryRepository in the comment & node modules is the one we're after.
- Let's also change to comment in the @todo, so it tells what we're trying to achieve. In case the newly linked issue changes it saves us the time of doing archaeology like we're doing in this issue.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3336491

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Spokje created an issue. See original summary.

spokje’s picture

Status: Active » Needs review
spokje’s picture

Issue summary: View changes
spokje’s picture

Assigned: spokje » Unassigned
smustgrave’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +Needs Review Queue Initiative

Simple fix and makes sense.

  • catch committed b4f93871 on 10.1.x
    Issue #3336491 by Spokje: Link to correct issue in @todo in...
catch’s picture

Status: Reviewed & tested by the community » Fixed

Committed b4f9387 and pushed to 10.1.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.