snicco / better-wp-api
This small package tries to solve the pain point of not being able to solve to scope code that references WordPress core code.
Requires
- php: ^7.4|^8.0
Requires (Dev)
- codeception/codeception: ^4.1.29
- lucatume/wp-browser: ~3.1.4
- phpunit/phpunit: ^9.5.13
Conflicts
- snicco/better-wp-cache: <2.0.0-beta.9
- snicco/better-wp-cache-bundle: <2.0.0-beta.9
- snicco/better-wp-cli: <2.0.0-beta.9
- snicco/better-wp-cli-testing: <2.0.0-beta.9
- snicco/better-wp-hooks: <2.0.0-beta.9
- snicco/better-wp-hooks-bundle: <2.0.0-beta.9
- snicco/better-wp-mail: <2.0.0-beta.9
- snicco/better-wp-mail-bundle: <2.0.0-beta.9
- snicco/better-wp-mail-testing: <2.0.0-beta.9
- snicco/better-wpdb: <2.0.0-beta.9
- snicco/better-wpdb-bundle: <2.0.0-beta.9
- snicco/blade-bridge: <2.0.0-beta.9
- snicco/blade-bundle: <2.0.0-beta.9
- snicco/content-negotiation-middleware: <2.0.0-beta.9
- snicco/debug-bundle: <2.0.0-beta.9
- snicco/default-headers-middleware: <2.0.0-beta.9
- snicco/eloquent: <2.0.0-beta.9
- snicco/encryption-bundle: <2.0.0-beta.9
- snicco/event-dispatcher: <2.0.0-beta.9
- snicco/event-dispatcher-testing: <2.0.0-beta.9
- snicco/guests-only-middleware: <1.0.0
- snicco/http-routing: <2.0.0-beta.9
- snicco/http-routing-bundle: <2.0.0-beta.9
- snicco/http-routing-testing: <2.0.0-beta.9
- snicco/https-only-middleware: <2.0.0-beta.9
- snicco/illuminate-container-bridge: <2.0.0-beta.9
- snicco/kernel: <2.0.0-beta.9
- snicco/kernel-testing: <2.0.0-beta.9
- snicco/method-override-middleware: <2.0.0-beta.9
- snicco/minimal-logger: <2.0.0-beta.9
- snicco/must-match-route-middleware: <2.0.0-beta.9
- snicco/no-robots-middleware: <2.0.0-beta.9
- snicco/open-redirect-protection-middleware: <2.0.0-beta.9
- snicco/payload-middleware: <2.0.0-beta.9
- snicco/pimple-bridge: <2.0.0-beta.9
- snicco/psr7-error-handler: <2.0.0-beta.9
- snicco/redirect-middleware: <2.0.0-beta.9
- snicco/session: <2.0.0-beta.9
- snicco/session-bundle: <2.0.0-beta.9
- snicco/session-psr16-bridge: <2.0.0-beta.9
- snicco/session-testing: <2.0.0-beta.9
- snicco/session-wp-bridge: <2.0.0-beta.9
- snicco/share-cookies-middleware: <2.0.0-beta.9
- snicco/signed-url: <2.0.0-beta.9
- snicco/signed-url-psr15-bridge: <2.0.0-beta.9
- snicco/signed-url-psr16-bridge: <2.0.0-beta.9
- snicco/signed-url-testing: <2.0.0-beta.9
- snicco/signed-url-wp-bridge: <2.0.0-beta.9
- snicco/str-arr: <2.0.0-beta.9
- snicco/templating: <2.0.0-beta.9
- snicco/templating-bundle: <2.0.0-beta.9
- snicco/testable-clock: <2.0.0-beta.9
- snicco/testing-bundle: <2.0.0-beta.9
- snicco/trailing-slash-middleware: <2.0.0-beta.9
- snicco/wp-auth-only-middleware: <2.0.0-beta.9
- snicco/wp-capability-middleware: <2.0.0-beta.9
- snicco/wp-capapility-middleware: <1.0.0
- snicco/wp-guests-only-middleware: <2.0.0-beta.9
- snicco/wp-nonce-middleware: <2.0.0-beta.9
- dev-master
- v2.0.0-beta.9
- v2.0.0-beta.8
- v2.0.0-beta.7
- v2.0.0-beta.6
- v2.0.0-beta.5
- v2.0.0-beta.4
- v2.0.0-beta.3
- v2.0.0-beta.2
- v2.0.0-beta.1
- v1.10.1
- v1.10.0
- v1.9.1
- v1.9.0
- v1.8.1
- v1.8.0
- v1.7.0
- v1.6.2
- v1.6.1
- v1.6.0
- v1.5.0
- v1.4.2
- v1.4.1
- v1.4.0
- v1.3.0
- v1.2.1
- v1.2.0
- v1.1.3
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.2
- v1.0.1
- v1.0.0
- dev-beta
This package is auto-updated.
Last update: 2024-11-07 15:05:55 UTC
README
BetterWPAPI is a single class that contains proxy methods for some of the most use WordPress core methods.
It's meant to be used in distributed WordPress libraries and helps you to keep your library testable and scopable.
Table of contents
Motivation
We developed this library for the WordPress related components of the Snicco project.
Directly interacting with core functions was problematic for us because:
- Code becomes untestable without
- a) booting the entire WordPress codebase or
- b) using additional mocking frameworks (mocking sucks).
- The code becomes really hard to scope using the de-facto standard tool PHPScoper.
- Static analysers like Psalm and PHPStan go crazy over core functions.
If you can't relate to these issues, you probably don't need this library.
Edit: The scoping problem was solved, by us creating
a command-line-programm that can be used to generate
a list of all functions and classes
in the entire WordPress core codebase. For now, the best example on how to use it
is the scoper.inc.php
configuration
of the Google Web stories plugin.
Installation
composer require snicco/better-wp-api
Usage
This is the public API of BetterWPAPI. No public or protected methods will be added until a next major version.
The idea is to limit the interaction with WordPress core to this class.
This has worked very well for us in order to keep our code testable and scopable. You have a single class where you can see all interaction that your library has with core. During tests, you can then simply swap this class with a test double.
The important thing is that: All classes that need anything from WordPress must accept this class as a constructor dependency.
A simple example: (for a real example, check out the BetterWPMail component)
Assuming we have the following class:
use Snicco\Component\BetterWPAPI\BetterWPAPI; class CSVImporter { public function __construct(BetterWPAPI $wp = null) { $this->wp = $wp ?: new BetterWPAPI(); } public function import(string $file){ if(!$this->wp->currentUserCan('import-csv')) { throw new Exception('Not authorized'); } // import csv. } }
This is how we use it in production code.
$importer = new CSVImporter(); $importer->import(__DIR__.'/orders.csv');
This is how we test the code. No bootstrapping WordPress needed.
class CSVImporterTest extends TestCase { /** * @test */ public function that_missing_permissions_throw_an_exception() { $this->expectExceptionMessage('Not authorized'); $wp = new class extends BetterWPAPI { public function currentUserCan():bool { return false; } } $importer = new CSVImporter($wp); $importer->import(__DIR__.'/test-users.csv'); } }
Contributing
This repository is a read-only split of the development repo of the Snicco project.
This is how you can contribute.
Reporting issues and sending pull requests
Please report issues in the Snicco monorepo.
Security
If you discover a security vulnerability within BetterWPAPI, please follow our disclosure procedure.