Closed (fixed)
Project:
Drupal core
Version:
8.1.x-dev
Component:
field system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
9 Jun 2015 at 11:01 UTC
Updated:
7 Aug 2016 at 16:33 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
xanoComment #4
berdirAre we sure that this really makes sense?
This is a field specific interface and various plugins there very much use it.
I'm not sure what impact this has in PhpStorm for example, are methods that are defined by this interface marked as deprecated?
That would definitely be wrong...
Comment #5
tim.plunkettHopefully the Drupal\Core\Field namespace will discourage people from using it, and stick to stuff in Drupal\Component\Plugin
Comment #6
berdirYeah...
I'd rather just explicitly document that this interface is specific to the field subsystem and other plugin types should use ConfigurablePluginInterface, without adding @deprecated or so.
Comment #7
mile23So is this a case of changed scope?
Comment #8
mile23Comment #9
alvar0hurtad0Working on this
Comment #10
alvar0hurtad0reroll
Comment #11
andypost8.1.0
Comment #12
uzlov commentedchanged to 8.1.0
Comment #13
uzlov commentedComment #14
uzlov commentedComment #15
berdirMakes sense. We don't want contrib to pick this up, they should use the other interface.
I applied this to try and make sure that it doesn't mark the interfaces/classes that implement this as deprecated. Works correctly.
Comment #16
alexpottCommitted fea9559 and pushed to 8.1.x. Thanks!
I removed the trailing * on the second line and formatted the comment to fit the standard in core.
Comment #19
claudiu.cristeaHm. But what about
PluginSettingsInterface::onDependencyRemoval()? As developer I'm advised to use ConfigurablePluginInterface but that doesn't have onDependencyRemoval().