Libraries tagged by alcon
particle-academy/fancy-conformance
106 Downloads
Shared cross-language conformance fixtures for the Fancy suite. One contract, N implementations, and a single table that every implementation asserts in its own CI — so 'parity' is a test result rather than a claim. Ships the fixture data itself alongside a small PHP loader.
oat-sa/extension-tao-booklet
13631 Downloads
An extension for TAO to create test booklets (publishable in MS-Word and PDF along with Answer Sheets)
nogrod/ebay-buy-browse-php-sdk
547 Downloads
The Browse API lets shoppers search eBay listings by keyword, category, GTIN, product, charity, compatibility criteria, or image, and refine results with filters such as aspects, compatibility, field values, and UI parameters through the item_summary resource.The item resource lets applications retrieve detailed information for a specific item or all items in an item group, and check whether a product is compatible with a specified item, such as whether a specific vehicle is compatible with a specific part. The item resource also supports legacy item identifiers alongside RESTful item IDs, which use different formats. This helps developers work with stored or historical legacy item IDs when using the Browse API.All methods in the Browse API require an Application access token, which is obtained using the client credentials grant flow.
mouf/javascript.underscore
145027 Downloads
This package contains the Underscore javascript library, along a Mouf installer file to add Underscore easily in your Mouf project.
mouf/javascript.syntaxhighlighter
145065 Downloads
This package contains the SyntaxHighlighter javascript library, along a Mouf installer file to add SyntaxHighlighter easily in your Mouf project.
mouf/javascript.jquery.jquery-ui
163638 Downloads
This package contains the JQuery UI library, along a Mouf installer file to add JQuery UI easily in your Mouf project.
mouf/javascript.jquery.jquery-filetree
145029 Downloads
This package contains the jQuery FileTree library, along a Mouf installer file to add JQuery FileTree easily in your Mouf project.
mouf/javascript.jquery.jquery
179023 Downloads
This package contains the JQuery library, along a Mouf installer file to add JQuery easily in your Mouf project.
mouf/javascript.historyjs
32957 Downloads
This package contains the History.js library, along a Mouf installer file to add History.js easily in your Mouf project.
mouf/html.template.bootstrap
241755 Downloads
This package contains a Mouf template based on the Twitter Bootstrap HTML/CSS/JS library, along a Mouf installer file to add the template easily in your Mouf project.
mohammad-zarifiyan/laravel-locale-kit
331 Downloads
A Laravel package that provides structured locale metadata alongside traditional translation files.
minasm/laravel-revisions
1168 Downloads
An update for from neurony. Create multiple revisions of any Eloquent model record along with its underlying relationships
macfly/yii2-tracker
29402 Downloads
Yii2 component to to track request for along all microservices app
letraceursnork/php-decliner
1318 Downloads
This repository offers a PHP-based solution for declension of nouns by grammatical cases along with numerals. It ensures correct noun forms based on case (nominative, genitive, etc.) and the numeral used, handling the specific rules of declension in supported languages.
konfig/snaptrade-php-7-sdk
608 Downloads
Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.