Abstract Query Class

[spacedmonkey]

All of the query classes WP_Comment_Query, WP_Network_Query, WP_Site_Query, WP_Term_Query and WP_User_Query are based on WP_Query class. For that reason they have a lot of similar methods and variables. As all the classes basically do the same thing, we can use an abstract class, so all related methods and variables are on the abstract class. If all query classes extend this abstract class, we can keep structure and consistency. It would also mean, for example, we could just add filters and actions in the abstract class and these would filter down.

[TimothyBlynJacobs]

Previously #15032.

[DrewAPicture]

@spacedmonkey Don't forget to add the has-patch keyboard when you add patches to tickets. Attachments don't trigger notifications :-)

[PieWP]

Think this is the beginning of something great, would love to some see constancy between the query classes.

If we can fix the following can we maybe set an actual version and maybe assign an owner of the ticket?

• Create unit tests
• Extend for WP_Term_Query
• Check backward compatibility
• Extends WP_Object_Query some more (WP_Query has some great features which can be made generic, and I think I saw the mention either in slack or some other tickets of making the meta_query usage available for other Query-classes)
• Align with coding standards (think bracket usage is of somewhere)
• Align with latest changes/developments (last patch was 17 months old)

More than willing to spend some time on this and creating a patch containing the points stated above if a core/lead developer can confirm wether the ticket/idea is actually desired.