Libraries tagged by explicit

Roles and permissions for Filament, built on elpandape/warden — a permission grid derived from your policies, explicit denials, and conditional grants.

Go to Download

Explicitly hydrate Pinia stores from Laravel responses.

Go to Download

Compiled, reflection-free JSON serialization with an explicit polymorphic type registry.

Go to Download

Human-readable workspace change review module for Neos CMS: word-level text diffs, editor-aware value labels, explicit visibility changes and per-page change summaries.

Go to Download

Standalone OpenAPI document builder for explicit PHP specifications.

Go to Download

This autoloader supports every autoloadable PHP feature up to PHP 5.4’s traits. It find’s every class, interface or traits definition in any situation. No matter what convention is used. The autoloader is index based. After building the index there will be no performance issue. The building is done dynamically. There is no explicit need of calling a build script. For the sake of comfortability there exists a script for prebuilding an index.

Go to Download

Extended and more explicit behavior for ActiveRecord classes for Yii2

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download

Explicit handling of type coercions and enforcement in PHP in order to deal with unknown data in a more predictable and safe way.

Go to Download

A modular router component for the Power Modules framework with encapsulated routing capabilities and explicit module integration

Go to Download

Concept Logger extension — Monolog with explicit handlers and optional data masking

Go to Download

Fragmented key cache invalidation library. Compose cache keys from independently versioned tags — increment a tag to invalidate all dependent keys without explicit deletes.

Go to Download

Saphpi, pronounced `sapi` is a web application framework that implements the MVC pattern. It's inspired by many popular frameworks and is designed to be explicit with batteries included.

Go to Download

A small, explicit PHP framework for conventional server-rendered applications.

Go to Download

DI-first infrastructure adapters providing explicit ownership wrappers around real database and cache drivers.

Go to Download