Download the PHP package phpnomad/fetch without Composer
On this page you can find all versions of the php package phpnomad/fetch. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download phpnomad/fetch
More information about phpnomad/fetch
Files in phpnomad/fetch
Package fetch
Short Description Client-side HTTP requests and strategies.
License MIT
Homepage https://github.com/phpnomad/core
FAQ
Example:
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 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.
Informations about the package fetch
phpnomad/fetch
phpnomad/fetch is the client-side HTTP abstraction for PHPNomad applications. It defines the FetchStrategy interface that application code depends on when it needs to make outbound HTTP requests, along with a FetchPayload value object and a fluent builder for assembling requests.
The package intentionally ships no transport of its own. Concrete implementations live in integration packages so your application code stays portable across runtimes. Pair it with phpnomad/guzzle-fetch-integration for Guzzle-backed transport, with the FetchStrategy in phpnomad/wordpress-integration for a wp_remote_request-backed transport, or write your own by implementing the interface. The same calling code works in every case. phpnomad/fetch powers outbound HTTP in Siren and several other PHPNomad-based systems in production.
Installation
You also need a strategy implementation. The common choices are phpnomad/guzzle-fetch-integration and the FetchStrategy included in phpnomad/wordpress-integration.
Quick Start
Build a FetchPayload and hand it to the strategy. The example below makes a GET request to a JSON API with a custom header and two query parameters.
The FetchStrategy instance is typically resolved from the container and injected into the services that need it. Because your code depends on the interface rather than a specific HTTP client, the same WidgetClient runs unchanged whether the underlying transport is Guzzle, wp_remote_request, or a custom implementation.
Key Concepts
FetchStrategyis the interface your application depends on. It exposes a single method,fetch(FetchPayload): Response.FetchPayloadis an immutable value object that carries the URL, HTTP method, headers, body, and query parameters for a single request.FetchPayloadBuilderprovides a fluent API for assembling a payload step by step when constructor arguments feel awkward.- The
Responsereturned byfetch()comes fromphpnomad/http, so status codes, headers, and body access are uniform across every transport. - To add a new transport, implement
FetchStrategyagainst the HTTP client of your choice and bind your implementation to the interface in your container.
Documentation
Full PHPNomad documentation lives at phpnomad.com.
License
Released under the MIT License.
