Overview & Architecture
Applied to a gateway element via data-ln-api-connector inside a coordinator tree, ln-api-connector encapsulates all connection parameters (base URLs, auth tokens, headers, and paths). It listens for request CustomEvents (ln-api-connector:request-query, create, update, delete), attaches a forced X-LN-Response: data header, and issues RESTful fetch() calls. Upon resolution, it parses JSON payloads and emits ln-api-connector:data or mutation response events to the parent coordinator.
In the decoupled 3-tier data lifecycle of ln-ashlar, the Transport Gateway owns all networking credentials and endpoints, remaining completely blind to database caches and schemas while keeping cache stores and UI presenters strictly network-agnostic.
Dynamic Configuration Synchronization
Mutating data-ln-api-base-url, data-ln-api-path, or data-ln-api-headers directly on the DOM element at runtime will instantly re-evaluate the instance configuration and dispatch ln-api-connector:config-changed.
Declarative Markup (Copy/Paste)
Interactive Playground & Telemetry
1. Mutation Observer (Dynamic Attributes)
Change these attributes in real-time to watch the MutationObserver hot-reload the connector configuration instantly.
2. Event Trigger Panel & Methods
Dispatch CustomEvents to trigger REST requests or use the programmatic JS API directly.