There are few places in core where {@inheritdoc} is {inheritdoc}.

core/modules/node/src/Tests/NodeTranslationUITest.php:20:   * {inheritdoc}
core/modules/shortcut/src/Tests/ShortcutTranslationUITest.php:17:   * {inheritdoc}
core/modules/menu_link_content/src/Tests/MenuLinkContentTranslationUITest.php:16:   * {inheritdoc}
core/modules/comment/src/Tests/CommentTranslationUITest.php:31:   * {inheritdoc}
CommentFileSizeAuthor
#2 2858021-2.patch2.26 KBshashikant_chauhan
#7 interdiff-2858021-2-7.txt3.34 KBjacobsanford
#7 2858021-7.patch2.46 KBjacobsanford

Comments

shashikant_chauhan created an issue. See original summary.

shashikant_chauhan’s picture

shashikant_chauhan commented
Status: Active » Needs review
StatusFileSize
new 2858021-2.patch2.26 KB

Adding patch for it.

krina.addweb’s picture

krina.addweb commented
Status: Needs review » Reviewed & tested by the community

@shashikant_chauhan,Thanks! for the patch it works well, so moved it to RTBC

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Reviewed & tested by the community » Needs work

Ideally we'd have a coder rule that enforces the correct format for {@inheritdoc}. There are also a number of occurrences of {@inheritDoc} whereas the standard and far more common case is all lowercase.

In order to fix this we should create the rule and fixer in coder. And then use this issue to apply the new rule to core and fix them. We should have a follow-up issue to extend the new coder rule to check that inherited doc blocks do not contain additional comments since this is not supported by api.drupal.org but is quite common in core.

See #2571965: [meta] Fix PHP coding standards in core, stage 1 and the many sub issues for how the process of fixing something like this in core should occur.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jacobsanford’s picture

jacobsanford
Primary language English
Location Fredericton 🇨🇦
commented
StatusFileSize
new interdiff-2858021-2-7.txt3.34 KB
new 2858021-7.patch2.46 KB

@shashikant_chauhan's patch in #2 no longer applied to 8.6.x. A reroll with no further modifications is attached.

The method suggested by @alexpott still is outstanding.

zahord’s picture

zahord commented
Status: Needs work » Needs review
borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Status: Needs review » Postponed

Postponing this on #2939783: @inheritdoc - check for misspelling

Anonymous’s picture

Anonymous (not verified) commented

More cases in the core:

  • iheritdoc,
  • @inheritdoc,
  • {@inheritdoc]
  • [@inheritdoc}
  • {inheritdoc}
  • {@inheritoc}
  • {@inheritdoc{
  • (@inheritdoc)

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Postponed » Closed (duplicate)
Issue tags: +Bug Smash Initiative
Related issues: +#3132287: Fix wrong usages of {@inheritdoc}, +#3138731: Fix "inheritdoc" typos in core

This has been fixed in #3138731: Fix "inheritdoc" typos in core and #3132287: Fix wrong usages of {@inheritdoc}. Closing as a duplicate.