Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
views.module
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 May 2015 at 13:22 UTC
Updated:
16 Jun 2015 at 04:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
catchComment #2
dawehnerHere is a list of plugin types!:
So we should add exposed forms.
Comment #3
catchAdding exposed forms.
Comment #4
dawehnerLooks perfect now!
Comment #5
catchComment #6
webchickMakes sense. My only question would be if it makes sense to have some sort of special annotation for these so we could
$plugins = Views::getPluginDefinitions('sometype');(obviously pseudocode) versus a hard-coded list. Else it seems like we are preventing contrib from extending here (but maybe that is fine).Comment #7
dawehnerWell, where would those annotations live? There is no formal definition of plugin types, beside the existence in the
.services.ymlfile and the hardcoded list in\Drupal\views\ViewsComment #8
damiankloip commentedThis looks good to me. This is not API changing/breaking either, as those PLUGIN types are the only ones we advertise a $theme property on (aside from the $register_theme property). All handlers are 'not allowed' anyway.
EDIT: didn't reload and just saw previous 2 comments, We could add a new method to the Views class. That is as good as it would get though I think. We don't really have a good way to get this info from the annotation metadata.
Comment #9
webchickOk, thanks for considering. Let's get this in in the meantime then.
Committed and pushed to 8.0.x. Thanks!