Libraries tagged by set query

A Database-Agnostic set of Abstractions built on top of PDO

Go to Download

Set of tools to build data set queries and attach them within http context

Go to Download

A set of helpful macros for Laravel Eloquent query builder

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

A set of models to use with Laravel's Eloquent to query a Wordpress database.

Go to Download

A set of two very lightweight hydrator components. The main usage of those hydrators would be to hydrate query results from joined tables into their respective nested objects.

Go to Download

A simple but effective way to set the table of a model at runtime and continue using Eloquent instead of QueryBuilder

Go to Download

Set url querystring params using PHP.

Go to Download

Adds a query parameter to the REST API for any CMB2 field that has the property rest_query set on it.

Go to Download

A set of Doctrine ORM QueryBuilder helpers

Go to Download

Clear previously set statements in Laravel query builder

Go to Download

A plugin that stores Google Analytics utm_parameter query string to a client cookies

Go to Download

Allows loading/including assets across multiple extended, but individually set up, applications

Go to Download

Set of functionalities enable Arabic website developers to serve professional search, present and process Arabic content in PHP

Go to Download

Advanced column filters for Laravel. Text, numeric, date and set filters with custom operators and strict allow-listing — declared once on an Eloquent model, then rendered with Blade + Alpine, Livewire, Inertia or as a JSON API.

Go to Download