Libraries tagged by hints

51degrees/fiftyone.devicedetection

1 Favers
18685 Downloads

Device Detection and User-Agent parser for PHP, built on the 51Degrees Pipeline API. Detects the device, browser, operating system, and crawlers from the User-Agent and User-Agent Client Hints, using the 51Degrees cloud service. An alternative to UAParser.js, DeviceAtlas, and WURFL.

Go to Download


vistik/typed-collections

11 Favers
28343 Downloads

A simple way to create typed collections in PHP - build on Illuminate\Support\Collection

Go to Download


wearejh/m2-module-jh-block-logger

29 Favers
1048 Downloads

Template/Block hints in the console.

Go to Download


waaseyaa/error-handler

0 Favers
8828 Downloads

Rich exception pages, solution hints, and editor links for Waaseyaa

Go to Download


samsara/roster

18 Favers
1187 Downloads

A PHP console tool to generate Markdown documentation from your docblocks and types hints using templates.

Go to Download


leonardo-max/new-here

1 Favers
438 Downloads

Show each user what is new right where it lives: pulsing beacons and contextual hints on the exact buttons, columns, fields and pages you just shipped in your Filament panel. Seen once per user, stored in the database, AI-agent ready.

Go to Download


konfig/snaptrade-php-sdk

1 Favers
25871 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.

Go to Download


attributes-php/validation

1 Favers
807 Downloads

Pydantic-inspired PHP library for validating data via type hints at lightning speed

Go to Download


artisanpack-ui/performance

0 Favers
4814 Downloads

Comprehensive performance optimization toolkit for Laravel applications: image optimization, JS/CSS strategies, resource hints, speculative loading, page and fragment caching, query analysis, and real-user performance monitoring.

Go to Download


nswdpc/silverstripe-field-hint

0 Favers
5565 Downloads

Allows developers to add usage hints for templates to consider when rendering the field

Go to Download


herrera-io/runkit-hint

5 Favers
36809 Downloads

A code hint file for the runkit extension.

Go to Download


xactsystems/type-hint-hydrator

0 Favers
1040 Downloads

A Symfony object hydrator based on declared types and annotation type-hints.

Go to Download


hryvinskyi/magento2-configuration-hints

6 Favers
650 Downloads

N/A

Go to Download


clesson-de/silverstripe-hints

0 Favers
187 Downloads

A Silverstripe CMS form field that displays a collapsible alert hint in the CMS edit form.

Go to Download


mindshape/mindshape_cookie_hint

6 Favers
71198 Downloads

Shows a visible hint on the website that cookies are used - according to the European laws. Easy to install, fully customizable and the hint will permanently be hidden after accepting.

Go to Download


<< Previous Next >>