Download the PHP package wp-oop/wordpress-interface without Composer

On this page you can find all versions of the php package wp-oop/wordpress-interface. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package wordpress-interface

Dhii - WordPress Interop

Continuous Integration Latest Stable Version Latest Unstable Version

Interfaces for interop within WordPress.

Details

Often, multiple packages need to operate on the various aspects of WordPress, while centralizing them. Unfortunately, many of these aspects are not represented by any type in WordPress. An example of this is a modular plugin, where each module needs to independently interface with such a part of WordPress that is centralized, like a Plugin or Post entity.

Also, it can be useful to write code that addresses a specific aspect of WordPress, and type-safety is desirable, but WordPress feels too bulky to include. While WordPress can be added as a dev-dependency, the dependency graph will not reflect these hidden requirements. For example, a Post type would be useful to represents a post.

In addition, some modules can be developed in a way to be usable in a variety of platforms. In these cases it would be necessary to rely on a proprietary standard.

This interop standard aims to address the above concerns by providing types for common aspects of WordPress.

All versions of wordpress-interface with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1 | ^8.0
dhii/package-interface Version ^0.1-alpha3
dhii/human-readable-interface Version ^0.2.0-alpha1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wp-oop/wordpress-interface contains the following files

Loading the files please wait ....