See #1513970: Convert SearchQuery to PSR-0 and #1513210: Meta: Start converting module provided classes to PSR-0 for more information.
This isn't strictly necessary because these two files are placed in files which are currently always includes. However, I guess we would all prefer if we could make these optional I guess :)
What I'm wondering is if we can find a way to prevent us from writing extend('Drupal\Core\Pager\PagerDefault') a million times. Could be a default namespace for extenders, or some sort of dependency injection? Would add a dependency on drupal_container() on the database component, as that works now.
Follow up: #1541892: Convert TableSort to PSR-0
Comment | File | Size | Author |
---|---|---|---|
#7 | 1541684-pager-7.patch | 35.88 KB | aspilicious |
#5 | 1541684.patch | 33.87 KB | RobLoach |
#2 | PagerSelectExtender.patch | 33.87 KB | RobLoach |
Comments
Comment #1
RobLoachLet's split TableSort off to its own issue to keep the patches simple :-) #1541892: Convert TableSort to PSR-0.
Comment #2
RobLoachComment #4
BerdirLooks like most if not all of the fails are caused by this:
Sounds like a missing use statement.
This was easy to type/remember before the conversion, now it's a lot harder. Also not sure if I like the name.
Comment #5
RobLoachThe PagerSelectExtender is a SelectExtender, which helps with pagers. Not sure what a better name for it would be.
Comment #6
aspilicious CreditAttribution: aspilicious commentedFull namespace paths needed in documentation.
Yeah the extenders will be harder to remember after the psr-0 conversion but we can't do anything about that if we don't want to introduce some kind of black magic. And the name sounds "sane". PagerDefault isn't a good name either for what it does.
18 days to next Drupal core point release.
Comment #7
aspilicious CreditAttribution: aspilicious commentedRerolled, lets get this in!
Comment #8
RobLoach#7: 1541684-pager-7.patch queued for re-testing.
Comment #9
RobLoachComment #10
RobLoachI'm tagging change notification early so we don't forget.
Comment #11
catchThanks! Committed/pushed to 8.x.
Comment #12
BerdirWe already have a change notice for the Search query extender, should we re-use that or create a new one? TableSort will follow soon....
Comment #13
catchJust one for all extenders seems alright to me.
Comment #14
aspilicious CreditAttribution: aspilicious commentedReview, fix the todo and make it better. Thnx!
http://drupal.org/node/1621062
Comment #15
RobLoachLooks good to me!
Comment #16
RobLoachComment #17
meba CreditAttribution: meba commentedHow does this affect Developer Experience?
Comment #18
aspilicious CreditAttribution: aspilicious commentedSee the change notice listed on top of this page: http://drupal.org/node/1621062
Comment #19.0
(not verified) CreditAttribution: commentedafsdfsdafd