The filter, post ID, or wp\u query parameters can safely check whether the wp\u post object is actually represented, while limiting the repetition of validation code everywhere. I repeat, this is actually too simple, showing the shortcomings of the factory model. Additional expenses that may not be worth it. However, as shown in this example, it can be used to introduce input validation, which has certain value. Carl Alexander has an excellent class design article, managing WordPress posts, which is worth reading when thinking about such factories. However, this is usually a good way to create systems with multiple application parts in a single configuration. For example, when you add a rest API endpoint or path set, you usually define the fields of the endpoint in the class that handles the path to which the endpoint belongs. But what if you need this configuration elsewhere? How do I inject configuration into endpoint generators and other generators? Then we will use the factory or other factories. Recently released the WordPress rest API endpoint generator that implements the factory pattern. While this is useful in itself, it works in libraries that use the same configuration, but we will create a copy creation interface that uses these endpoints. Since the configuration is loosely connected with the code, it is hoped that angular can apply the UI to adopt the fields API specification after it is created and completed. Another place where factories can be useful is plug-ins. Plug ins usually have similar add ons, use the same hook, and use a lot of duplicate code. One use of factory mode is to automatically set all hitches. One of the reasons for using the word press core global monochrome PHP design pattern is that you do not need to use global variables to store instances of classes. A single ton does not use global variables, but introduces global and other states into the application. PHP global variables are completely changeable. Settings can be turned off or redefined at any time. We all agree not to change the global $post variable of WordPress to an array, but we can. It is illegal to change the global $post to any array or disable the post\u title attribute. A fatal error may occur on the next visit. The WordPress kernel does not use monochrome. Although not exactly, it is likely to be an artifact of WordPress and earlier versions of b2\/cafelog launched before the introduction of static attributes into PHP. Instead, WordPress puts many class instances into global variables. These classes tend to have public creators. For wp\u rewrite closely associated with the saved rewrite rule, it is almost impossible to need wp\u rewrite instances except those in the global $wp\u write. If WordPress had been written today, wp\u rewrite might have implemented monochrome mode. Instead: Global $wp\u rewrite;
$wp\u rewrite->flush\u rules(); We may use: wp\u rewrite::get\u instance() ->flush\u rules(); But this may be an overuse of monochromatic PHP design patterns. You can have a default word press class with monochrome and instances of wp\u rewrite, wpdb, wp\u rest\u server, etc. Global$wp_rewrite is a pure technical liability incurred when the project is more than 10 years old, and promises not to damage the compatibility with previous versions. And I’m sure that more \
No teeth. For reusable classes with \
