We are working on a proposal to add the use of the @since documentation tag to the coding standard for core. The idea is to use it for new functions added to Drupal core in point releases.

Today it is quite difficult for a contrib developer to know if a core feature they use was introduced in the X.0 release or a later point release. Thanks to automatic testing and other things, many new features have been introduced for Drupal 7 than what happened for Drupal 6.

If coder would be able to parse it, then it could also advice contrib developers that they need to change the value for the "core" keyword in the .info file to the correct core version based on this.

Would this be possible to add to the coder module when/if the #1462360: [policy] Use @since tag for new functions/arguments added in point releases (>7.0, >8.0, etc.) lands?

Comments

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Coder 7.x-1.x is frozen now and will not receive any updates. Coder 8.x-2.x can be used to check code for any Drupal version, Coder 8.x-2.x also supports the phpcbf command to automatically fix conding standard errors. Please check if this issue is still relevant and reopen against that version if necessary.