You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7e29597
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(provider-core): follow the Effect service conventions throughout
An audit of every provider-core module against
docs/internals/effect-services.md:
- No standalone Shape interfaces: IdAllocatorV2, ProviderAdapterV2, and
ProviderHost define their interface inline; consumers use
`X["Service"]`. IdAllocatorV2's sub-records drop the Shape suffix.
- Service modules are PascalCase and utility modules camelCase:
continuationRequests becomes ProviderContinuationRequests (with a
matching key), and ProviderAuthFlow becomes providerAuthFlow (it
defines no service).
- Imports from service modules (IdAllocator, ProviderAdapter,
ProviderHost, ProviderEventLoggers, ProviderContinuationRequests,
ModelCatalog) are namespace imports everywhere they are used.
- Services come from the environment, not parameters:
makeProviderSnapshotSettingsSource yields ProviderHost, and the
failure turn-item helpers use the pure IdAllocator.derive, now a
top-level export the layer reuses.
- No re-export shims: the server's ProviderEventLoggers module becomes
ProviderEventLoggersLive (its layer only), and consumers import the
tag from provider-core.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments