Libraries tagged by ei

A CodeSniffer sniff that requires that all classes be either abstract or final

Go to Download

A validation library using Either from marcosh/lamphpda

Go to Download

Content-Elemente können ganz einfach per Drag & Drop in die Artikel an beliebige Positionen gezogen werden.

Go to Download

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.

Go to Download

Determine your project version from either a commit.json or from your git repository.

Go to Download

GSB11 Permission collection for the Goverment Site Build (GSB) 11. Der GSB 11 ist eine Maßnahme der Dienstekonsolidierung Bund (DKB) des Bundesministeriums des Innern und für Heimat (BMI) und wird im Auftrag des Informationstechnikzentrums Bund (ITZBund) durchgeführt.

Go to Download

CLIProxyAPI for Laravel: a laravel/ai driver over either wire protocol, gateway-first routing with a fallback of your choice, the management API, and batches run as queued calls.

Go to Download

Aktiviert einen Dark Mode im Backend.

Go to Download

„Sicherung" im Backend (unter System): Datenbank-Backup und alle relevanten Dateien/Ordner als ZIP herunterladen oder auf dem Server ablegen, als Installationspaket für den Contao Manager exportieren – und Backups wiederherstellen (aus var/backups, per ZIP-Upload oder aus einem auf dem Server liegenden Archiv).

Go to Download

Generate feeds in either RSS 1.0, RSS 2.0 or ATOM formats

Go to Download

Warren — a Reddit-inspired theme for Flarum 2. Compact post rows with a vote pill, image and text previews, Hot/New/Top sorting, a collapsible rail and threaded comments. Shares fof/gamification's vote tables, so nothing is lost either way.

Go to Download

Übergangspaket ohne Code: Ekkon (Task-System, Benachrichtigungen, Webhook-Eingang) ist fester Bestandteil der Intranet-Plattform. Das Paket erfüllt nur noch bestehende require-Einträge.

Go to Download

Ermöglicht es im Backend Notizen zu erfassen. Optional können diese auf dem Dashboard der Contao-Startseite publiziert werden. Damit ist es möglich einem Backend Benutzer Informationen wie Farbdefinitionen, Bildgrössen, Kurzanleitungen oä. zu zeigen.

Go to Download

Add modules to easily manage your records (insert, edit & export in be/eId) in one place.

Go to Download

Es ist möglich aus einem Git Commit anhand von metadaten ein Changelog zu generieren, dass Leserechte hat

Go to Download