DWS WP Framework
  • Welcome
  • Primary goals
    • Modular design
    • No 3rd-party dependencies
  • Key concepts and dev tools
    • PHP and WP requirements
    • Object-Oriented Programming
    • Semantic Versioning
    • Version Control (git / GitHub)
    • Dependency Management (Composer)
    • Automated Testing (Codeception + Github Actions)
    • Dependency Injection (PHP-DI)
    • Coding Standards (PHPCS and PHPMD)
    • Dependencies Scoping (PHP-Scoper)
    • TypeScript and Sass
    • Task Runners (Grunt)
  • Setting up your dev environment
    • Windows
  • Your first plugin
    • Multiple plugins using the framework on the same site
  • Frequently Asked Questions
  • Bootstrapper Module
    • Motivation
    • How it works
    • How to use
    • White Labeling
  • Helpers Module
    • Motivation
    • How to use
  • Foundations Module
    • Motivation and How to use
    • Actions
      • Local action traits
      • Extension action traits
      • Integration action traits
    • States
    • Utilities
      • Stores
      • Handlers and Services
        • Logging Service
  • Plugin
    • Main Plugin Instance
    • Plugin Components
  • Hierarchies
  • Helpers
  • Utilities Module
    • Motivation and How to use
    • Hooks Service
      • Scoped Handler
    • Shortcodes Service
    • Templating Service
    • Assets Service
      • Scripts Handler
      • Styles Handler
    • CRON Events Service
      • Action Scheduler Handler
    • Admin Notices Service
    • Dependencies Service
    • Validation Service
  • Core Module
    • Motivation and How to use
    • Plugin Tree
      • Plugin Root
      • Plugin Functionality
    • Plugin Components
      • Internationalization
      • Installation / Upgrade / Uninstallation
  • Settings Module
    • Motivation and How to use
    • Settings Service
      • WordPress Handler
      • MetaBox Handler
      • ACF Handler
    • Validated Settings
  • WooCommerce Module
    • Motivation and How to use
    • Extended WC Logger
    • WC Settings Handler
Powered by GitBook
On this page

Was this helpful?

  1. Utilities Module

Motivation and How to use

PreviousHelpersNextHooks Service

Last updated 4 years ago

Was this helpful?

The Utilities Module is where all the other services are. If you don't remember from the foundations module's documentation, are a abstract wrappers around concrete implementations for fulfilling given actions. For example, the foundations module comes with pre-packaged with .

Services are meant to be singletons. Usually they register one or multiple handlers for performing the actual actions with (like how the logging service required two logging handlers, one for the framework itself and one for the actual plugin).

The module is available for free installation through . We'll explore the pre-packages services in this documentation.

As of April 2021, the Utilities Module is still considered in beta. Beta modules don't have automated tests yet and can change significantly until the release. However, the overall structure is clear and done. You may use it but it might be wise to keep an eye out for undocumented changes.

If you get confused while reading the documentation, don't forget to take a look over our . There are examples there of using some of the services described here.

services and handlers
a logging service
Composer
on Packagist
example plugin on GitHub