Libraries tagged by null values
schnittstabil/get
113681 Downloads
Get nested array values and object properties.
jessegall/php-types
2141 Downloads
Named typed constants and predicates — give meaning to magic literals like '', [], '{}', 0, true and null.
holgerk/assert-golden
11849 Downloads
Same as assertEquals, but when null is given as argument, the test file is automatically edited and null is substituted with the actual value
sil-org/php-env
6377 Downloads
Simple PHP library for getting (or requiring) environment variables, designed to handle true, false, and null more intelligently. If desired, an environment variable's value can be split into an array automatically.
silinternational/php-env
54780 Downloads
Simple PHP library for getting (or requiring) environment variables, designed to handle true, false, and null more intelligently. If desired, an environment variable's value can be split into an array automatically.
rekalogika/file-null
4262 Downloads
Null object pattern implementation for rekalogika/file framework.
adammbalogh/key-value-store-null
27272 Downloads
Key-value null store package. It literally does nothing.
awd-studio/vo-optional-php
312 Downloads
Type-safe Optional value object for PHP 8.4+. A robust implementation of the Optional pattern inspired by Java, providing elegant null-safety and functional programming capabilities.
n2n/n2n-util-serialize
266 Downloads
Safely serialize and unserialize plain data objects (PHP native serialize()/unserialize() with an allowed_classes allowlist derived from the class structure) and scalar/null values (JSON), preventing object-injection and POP-chain attacks.
crivion/options
1520 Downloads
A way to get_option($option_name, $default = null) and set_option($option_name, $option_value) similar to wordpress for Laravel.
xakepehok/value-object-builder
6602 Downloads
This helper can create object from passed classname and value, or return null, if passed value is also null
zippendo/zippendo-php
15 Downloads
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`.
cvsouth/cache-null
1325 Downloads
Enables support for caching of null values in Laravel
crissi/laravel-cursor-pagination-with-null-values
5 Downloads
Laravel cursor pagination with null values
bigchicchicken/api-platform-skip-null-bundle
123 Downloads
Bundle to globally define skip_null_values parameter on all entities for ApiPlatform