Repository navigation
AdapterKeys
Viames Marino edited this page Oct 19, 2026
·
1 revision
Pair\Core\AdapterKeys defines the conventional capability names used by AdapterRegistry and application bootstrap. It has constants only and cannot be instantiated.
| Constant | Registry key |
|---|---|
CACHE |
cache |
MAILER |
mailer |
OBSERVABILITY |
observability |
PAYMENTS |
payments |
NOTIFICATIONS |
notifications |
AI |
ai |
UI |
ui |
use Pair\Core\AdapterKeys;
use Pair\Core\Application;
use Pair\Services\StripeGateway;
$app = Application::getInstance();
$app->setAdapter(AdapterKeys::PAYMENTS, $stripeGateway);
$payments = $app->adapters()->require(AdapterKeys::PAYMENTS, StripeGateway::class);The registry also accepts application-owned string keys. A constant does not install an integration or load a provider SDK. Application::setAdapter() additionally connects OBSERVABILITY to the observability facade when the adapter implements ObservabilityAdapter. Other keys store adapters for explicit retrieval; cache stores and UI renderers still require their own registration APIs.
See also: Application, AdapterRegistry, Integrations, CacheStore, ObservabilityAdapter, UiRenderer.
Home · Setup · Configuration
Build with Pair 4
- Generator
- Controllers and responses
- Read models
- ActiveRecord and queries
- Forms and validation
- PairUI.js and HTML fragments
APIs and authentication
- API guide and CRUD
- Middleware and rate limits
- Users, sessions, and ACL
- Passkeys and social login
- Native mobile setup
Integrate and operate
- Integrations
- Runtime extensions and adapter keys
- Cache and cache stores
- Logs and observability
- PWA and push
- Packages and distribution
- Upgrade to v4