netglue / prismic-asset-api-client
Requires
- php: ~8.3 || ~8.4
- cuyz/valinor: ^1.14
- fig/http-message-util: ^1.1
- psr/http-client: ^1.0
- psr/http-factory: ^1.1
- psr/http-message: ^2.0
Requires (Dev)
- doctrine/coding-standard: ^12.0
- laminas/laminas-diactoros: ^3.5
- php-http/curl-client: ^2.3.3
- php-http/mock-client: ^1.6.1
- phpstan/extension-installer: ^1.4.3
- phpstan/phpstan: ^2.1.5
- phpstan/phpstan-phpunit: ^2.0.4
- phpstan/phpstan-strict-rules: ^2.0.3
- phpunit/phpunit: ^12.0.2
- psalm/plugin-phpunit: ^0.19.2
- squizlabs/php_codesniffer: ^3.11.3
- vimeo/psalm: ^6.5.1
Conflicts
- php-http/httplug: <2.4.1
- php-http/promise: <1.3.1
README
This is a client for Prismic.io's Asset API.
You can find documentation on the API at prismic.io/docs/asset-api-technical-reference
Install
composer require netglue/prismic-asset-api-client
Usage
You'll need to construct the concrete client yourself with all of its required dependencies:
- A PSR-18 HTTP Client such as php-http/curl-client
- PSR-7 implementations with PSR-17 Stream Factory, Request Factory and Uri Factory such as laminas/laminas-diactoros
Assuming you have a PSR-11 container set up, you might be able to do something like this in a factory:
use Prismic\Asset\AssetClient; use Psr\Http\Client\ClientInterface; use Psr\Http\Message\RequestFactoryInterface; use Psr\Http\Message\StreamFactoryInterface; use Psr\Http\Message\UriFactoryInterface; $client = new AssetClient( 'some-write-token', 'some-repo-name', $container->get(ClientInterface::class), $container->get(RequestFactoryInterface::class), $container->get(UriFactoryInterface::class), $container->get(StreamFactoryInterface::class), );
Basic Functionality
Fetch a list of the current asset tags
use Prismic\Asset\Client; assert($client instanceof Client); $tags = $client->getTags();
Manually add an asset tag
use Prismic\Asset\Client; assert($client instanceof Client); $tags = $client->createTag('Some Tag');
List Assets
This library assumes that you'll probably want to use it for doing a migration, so the listAssets
method fetches all asset details in batches of 10 (The max result set size).
This is likely to take a long time on a large media library…
use Prismic\Asset\Client; use Prismic\Asset\Model\Asset; assert($client instanceof Client); /** @var list<Asset> $assets */ $assets = $client->listAssets();
Upload Assets
The uploadAsset
method requires the file content as a string, a name or title for the file and its mime type.
There are a number of optional fields for other file metadata such as its default alt
attribute, private notes, copyright info and applied tags.
use Prismic\Asset\Client; assert($client instanceof Client); $asset = $client->uploadAsset( $fileContentsAsString, $fileBaseName, $mimeType, );
Update Asset Meta Data
All values except the identifier are optional. Replacing any other value with null
will omit the field from the patch entirely.
To remove values, you must supply empty strings, or in the case of tags, an empty array.
It is not possible to "nullify" asset properties, even sending null in the JSON payload will yield an asset with an empty string for that value.
use Prismic\Asset\Client;use Prismic\Asset\Model\AssetPatch; assert($client instanceof Client); $updatedAsset = $client->patchAssetMetaData(new AssetPatch( 'some-asset-identifier', 'New private notes content', 'New copyright info', 'New alt attribute', 'updated-filename.txt', ['tag 1', 'tag 2'], ));
Tags are automatically created
During asset upload, or patch, tags are created automatically so both methods accept a list of tag names i.e. ['tag 1', 'tag 2']
saving you from mucking about with tag lists and tag id's.
Contributing
Please feel free to get involved with development. The project uses PHPUnit for tests, and Psalm and PHPStan for static analysis. CI should have your back if you want to submit a feature or fix ;)