You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As WordPress continues to be the primary focus of this project, many of the classes currently use WordPress specific function calls.
One of the longterm goals of this project, is for it to be platform and environment agnostic. For this to happen, anything specific to WordPress needs to be abstracted into some type of middleware.
Without looking, wp_parse_args and sanitize_key() come to mind. There are probably at least a dozen functions being used.
The text was updated successfully, but these errors were encountered:
I have a plugin boilerplate that abstracts most functionality across key forms plugins. I created an abstract class, Form that is extended by each of the major forms plugins. Gravity_FormsNinja_Forms, etc.
Each of these extensions implement key abstract methods that are used to handle the fundamental functions that any forms plugin can do. Create forms, delete forms, etc.
The Forms class is accessed using a function that automatically detects which forms plugin should be used, and returns the correct instance.
I wonder if this would be a good strategy to implement for these WordPress specific functions within Berlin, as well? This would provide a clear set of methods that would need to be created in-order for Berlin to support other platforms.
As WordPress continues to be the primary focus of this project, many of the classes currently use WordPress specific function calls.
One of the longterm goals of this project, is for it to be platform and environment agnostic. For this to happen, anything specific to WordPress needs to be abstracted into some type of middleware.
Without looking,
wp_parse_args
andsanitize_key()
come to mind. There are probably at least a dozen functions being used.The text was updated successfully, but these errors were encountered: