Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
field system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Oct 2015 at 08:32 UTC
Updated:
13 Nov 2015 at 20:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
joshi.rohit100Comment #3
yched commentedLooks good, thanks
Comment #5
rakesh.gectcrComment #6
yched commentedThanks @rakesh.gectcr. So addConstraint() is impacted too ? Can we add it to the issue title and summary ?
I'm not where I can check the interface atm, so not setting to RTBC myself, anyone feel free.
Also, this should be ok to get in during RC phase, since it's fixing an incorrect interface implementation, and will not cause any code break. Adding the triage tag to let committers decide.
Comment #7
rakesh.gectcrComment #8
rakesh.gectcr@yched
I have added that into issue summary.
Comment #9
swentel commentedYep, addConstraint wants it back to.
Comment #10
xjmDiscussed with @alexpott, @effulgentsia, and @catch. This is mostly a coding standards improvement based on: https://www.drupal.org/node/608152#chaining
This does change the return values of these functions, but I can't really imagine that any code could possibly need to rely on the fact that these methods always return NULL in HEAD.
I also checked and confirmed that all three methods already have documentation that the method returns
$this. So committed and pushed to 8.0.x. Thanks!