When for example extending a Query with PagerDefault and that has an error, the error tells you only that you are using PagerDefault but not where :)

Patch simply checks if the class implements QueryExtendableInterface...

Comments

Crell’s picture

Status: Needs review » Needs work

Shouldn't it be SelectQueryExtender? QueryExtendableInterface is the one on Select itself, saying it CAN be extended. It's not what's on the ExtendER, but the ExtendEE.

berdir’s picture

every extender can be extended itself, so it doesn't really matter :)

SelectQueryExtender implements SelectQueryInterface which extends QueryExtendableInterface.

So any of these works technically but I'm happy to change it if you think that another one makes more sense logically.

Crell’s picture

Well bah!

I suppose we could do both... I mean, we want to skip both of them in the stack trace, right? :-)

berdir’s picture

Status: Needs work » Needs review
StatusFileSize
new924 bytes

Hm, I don't think both makes any sense because SelectQueryInterface extends from QueryExtendableInterface, so checking SelectQueryInterface automatically includes QueryExtendableInterface.

However, in all other Places where we check an interface, we use SelectQueryInterface, so I updated the patch to use that one.

Status: Needs review » Needs work

The last submitted patch, filter_out_extenders2.patch, failed testing.

berdir’s picture

Status: Needs work » Needs review

#4: filter_out_extenders2.patch queued for re-testing.

Status: Needs review » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.