Libraries tagged by melon

The smallest Laravel package for having User belongs to relation

Go to Download

BelongsTo field for laravel nova which allows to choose or create a resource

Go to Download

Nested set model for Eloquent in Laravel package.

Go to Download

Belongs To One Laravel 5 Relation class

Go to Download

belongsToMany nova representation in field.

Go to Download

Trait for models that can belong to either a user or a guest session

Go to Download

A lightweight implementation of Laravel's BelongsToMany relationship

Go to Download

BelongsToMany nova representation in field.

Go to Download

Fun project: Quote randomizer built in VanillaPHP, comes with Elon Musk quotes for the win.

Go to Download

Nova vue-tree-select field for management nested category relations.

Go to Download

This package adds Traits for generating UUIDs and filling audit columns on Models, extends fico7489/laravel-pivot to add UUIDs to Pivot Tables

Go to Download

Extension of Laravel's Eloquent relationships: additional relationship types, query joins, pivot models, converters and helpers

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. 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

Optimize Laravel queries using SQL JSON aggregation (belongsTo/hasOne/hasMany in a single query)

Go to Download

Search and sort Eloquent queries and Filament tables by a person's full name across first_name and last_name columns, with BelongsTo and HasOne relation support and multi-token matching.

Go to Download