Coming from http://drupal.org/node/1839078#comment-6743488:

  • TypedData classes refer to interfaces without using their namespace. That's only valid if the namespace is imported, but partly that's not the case.
  • TypedData array keys use names with spaces, e.g. 'list class'. Since we are using annotations we've migrated to go with underscores everywhere now. Finally consistentcy, so let's follow that.
  • To avoid issues with late static binding, we should avoid using self::. But current field item implementations do so - replace that self usages with static.

Let's save us some pain and postpone this until bigger patches like #1778178: Convert comments to the new Entity Field API made it in.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

fago’s picture

Issue tags: +typed data
mgifford’s picture

Issue summary: View changes
Status: Postponed » Active
Related issues: +#1778178: Convert comments to the new Entity Field API
Arla’s picture

Component: base system » typed data system
FileSize
7.76 KB

Found (and fixed) some bad doc-comments with

grep -r ' \* Implements \\' core/lib/Drupal/Core/TypedData/
grep -r '@param \$' core/lib/Drupal/Core/TypedData/
mgifford’s picture

Status: Active » Needs review

Great. Thanks @Arla

Status: Needs review » Needs work

The last submitted patch, 3: typeddata-doc-1844112-3.patch, failed testing.

Arla’s picture

Status: Needs work » Needs review
FileSize
7.41 KB

Reroll

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.

borisson_’s picture

Status: Needs review » Closed (duplicate)

We don't really do these kinds code/documentation style updates per module.