- π³πΏNew Zealand quietone
Reading the issue summary, this belongs in the core queue. It is not about the Drupal project, more internal implementation, and developer experience.
I don't see how this would work in practice because MRs can have changes across many files. How does one choose where to put a comment with a link to the change record? And if we decided to place the info in the api.php or some high level interface then those files would have an ever growing list of links to change records. Or at least a list that needs to be maintained.
I think the easiest and best solution to improve documentation is to actually write it, whether that is in the core queue or in the handbook. And I do appreciate the challenges of doing that as I have done it myself, sometimes it was easy and sometimes quite difficult and even frustrating. And also, the handbook is a wiki, anyone can edit it at any time. That can help in some cases.
- Status changed to Closed: won't fix
9 months ago 3:49am 6 August 2024 - π³πΏNew Zealand quietone
I came across this again today. Except for my comment there hasn't been any discussion here about this, pro or con. Since there is no interest I am closing this as won't fix.
If you disagree, by all means, add a comment explaining your view and set the status to active.