Closed (fixed)
Project:
Drupal core
Version:
8.4.x-dev
Component:
menu system
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
28 Apr 2017 at 15:55 UTC
Updated:
20 Apr 2018 at 19:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
maryedith commentedadding patch to link @deprecated to change record
Comment #3
johnshortessThis looks good to me. The added comment appears to be linking to the correct change record, the format matches that in the parent issue, and there's no stray whitespace.
Comment #4
johnshortessOops, missed that the format in the parent issue has a blank line before the @see.
Comment #5
johnshortessHere's a new patch with the added blank line.
Comment #6
johnshortessWrong patch. Here's the right one.
Comment #9
johnshortessRe-roll.
Comment #10
edwdeapri commentedReviewing now - Baltimore
Comment #11
edwdeapri commentedSuccessfully applied patch. Reviewed changes to code. There are further @deprecated instances within file. Line 122 and 135.
Comment #12
edwdeapri commentedComment #13
maryedith commentedYes, -the other 2 @deprecated lines in the code don't exactly fit under the same change record as the first, -and there is not an exactly matching change record. Shall we make a change record for menu_primary_local_tasks() and menu_secondary_local_tasks()?
Comment #14
edwdeapri commented@maryedith - Yes. During DrupalCon Baltimore sprints, we were asked that all @deprecated lines needed an original corresponding change record. New ones would need to be created for change records that didn't exist.
Comment #15
quietone commentedHey, thanks for doing all this work on the deprecations and change records.
The changes are to menu, so moving to the menu system.
@maryedith, it looks like you meant to make a comment and not add a long issue tag in #13. Maybe you could edit your comment?
Edit: Sorry, I didn't intend to delete the issue tag.
This is the text that was in the issue tag and really looks like it should have been a comment in #13.
Yes, -the other 2 @deprecated lines in the code don't exactly fit under the same change record as the first, -and there is not an exactly matching change record. Shall we make a change record for menu_primary_local_tasks() and menu_secondary_local_tasks()?
Comment #16
maryedith commentedOk, I tried my hand at making a change record:
https://www.drupal.org/node/2874695.
this change record applies to both menu_primary_local_tasks() and menu_secondary_local_tasks()
Comment #17
maryedith commentedchanged title of this issue to not include the line #
Comment #18
mile23Thanks for making a change record https://www.drupal.org/node/2874695
It really shouldn't be published before this issue is fixed, but no biggie. It does tell you how to work around the deprecation, but it doesn't link to the issues in question.
Updated the CR. Maintainer please remember to publish it. :-)
Added this issue to existing CR https://www.drupal.org/node/2544940
Code patch applies and adds appropriate @see, checked using git -L.
Comment #20
catchIn this case it'd be fine for the change record to be published since the deprecation already happened, it was just missing the change record.
Committed 4ba925c and pushed to 8.4.x. Thanks!
Comment #22
kay_v commentedRemoving parent issue per conversation with @xjm at Drupalcon Nashville Mentored Sprint prep. Her recommendation to do so was based on a few points that made sense to all of us in the discussion, namely:
- so many child issues makes this parent unwieldy
- search filters will allow people needing to refind closed children