Libraries tagged by Three Q
zetacomponents/tree-persistent-object-tiein
4000 Downloads
The Tree component handles the creating, manipulating and querying of tree structures. This component uses persistent objects as data storage for the data elements of the tree nodes.
zetacomponents/tree-database-tiein
4132 Downloads
The Tree component handles the creating, manipulating and querying of tree structures. This component implements the database related backends and data stores.
zetacomponents/tree
4190 Downloads
The Tree component handles the creating, manipulating and querying of tree structures. The component supports different storage algorithms for optimal performance.
zxf/tools
489 Downloads
第三方登录、条形码Barcode、二维码QrCode、生成菜单、发送短信、图片处理、随机数、字符压缩、文字转图片、生成数据字典、远程截图、Redis、laravel多模块应用和一些常用方法集合等
mathieuviossat/fibonacci-heap
156 Downloads
PHP implementation of the Fibonacci heap
kode/tools
67 Downloads
PHP8.1+通用工具包,包含消息体、数组处理、字符串处理、时间处理、加解密、IP、地理计算、Curl、二维码、全局辅助函数等
kariricode/data-structure
1097 Downloads
The KaririCode DataStructure component offers advanced PHP data structures, including lists, stacks, queues, maps, and sets. It features efficient, strongly-typed, object-oriented implementations like ArrayList, LinkedList, BinaryHeap, and TreeMap.
edulazaro/larameter
4 Downloads
Credits, plans and quotas for Laravel: sell an allowance per window and top-ups on the side, cap how many seats or projects a plan allows, work out which plan an account is on, and stop a call before it spends what is no longer there. Nothing to do with AI in particular.
qufo/mptt
5 Downloads
modified preorder tree traversal algorithm helper for laravel/lumen
kryption/laravel-mediahub
9 Downloads
Multi-tenant media library for Laravel: folder tree, trash, quotas, derivatives, streamed archives and signed URLs.
topshelfcraft/ranger
53632 Downloads
What roads would any dare to tread, what safety would there be in quiet lands, if the Dunedain were asleep?
zippendo/zippendo-php
7 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`.
trm42/cache-decorator
247 Downloads
Magical (as in saves manual work quite a lot) Cache Decorator for Laravel 5. Designed for usage with repositories but easily usable for other uses. If there's enough interest, can be made framework agnostic.
yuriitatur/query-builder
114 Downloads
A simple package to build query node tree
quanzo/yii2-tree
1 Downloads
Ajax tree mapping. Adjacency list tree type. The ability to change the structure.