SIGNALS Docs
Reader View

Plugin SDK coming soon

Honest roadmap for Plugin SDK capabilities that are not shipped yet — the only place aspirational plugin documentation may live.

About this page

The roadmap tables below contain planned or deferred capabilities. They are separate from the shipped capabilities linked here; a related core contract does not itself promise a stable plugin API.

Shipped guides start at Plugin SDK.


Import/export registrations (no manifest declaration required), dashboard widgets, the registrar interface, paginated PluginContext::list() queries, PluginJob, schedules, capability consent and the package test kit are shipped. See Runtime, Jobs and schedules, Upgrades and Testing plugins.

Data layer

Item What / why later
General query builder Joins and arbitrary query expressions beyond the shipped, allowlisted list() filters
Data delete The manifest accepts delete, but it grants nothing; there is no SDK delete method
Named domain scopes Safer reusable query scopes without exposing Eloquent
raw_read Controlled escape hatch for advanced reads; high risk of leaking undeclared fields
Core API response filters Let plugins shape REST payloads; needs stable filter contracts and performance review

UI

Item What / why later
Marketing-style plugin listings in the Plugins admin Warehouse-front detail panels in the manager UI. (Plugin-owned UI pages — nav + pages[] rendered at /plugins/{vendor}/{name}/{page} — are shipped; see Plugin UI)
Slot component enforcement The supported component catalogue is documented but registration does not enforce it

Hooks & automation

Item What / why later
Decorator core call-sites Handlers + dispatcher exist; core does not yet invoke Decorator at domain call-sites. Validator (assignment.creating) and Filter (assignment.query) call-sites are available, along with Event + AuditableEvent bridges.
Approval and report definitions Additional stable APIs for approval actions and report definitions; dashboard widgets already ship through the widget bridge

Testing & DX

Item What / why later
Additional execution spies Richer observation tools beyond the shipped connection, principal, typed slot, action and refresh helpers, manifest builders, hook fakes and Laravel HTTP fakes

Scanning

Item What / why later
Scan context handlers as first-class SDK chapters Scanning contracts exist in core; deeper plugin-facing docs/API polish TBD

Do not rely on these yet

General query builders are unavailable; allowlisted list() queries are supported. The supported SDK surface is: Event hooks + data facade, slots (all families + modals.global), nav groups + config-driven pages, datatables (datatable() / datatableSlot() and the datatable page section), palette providers, recents, plugin notifications (PluginContext::notify), provided events (PluginContext::emit), import/export registrations, and vendor-namespaced workflow handlers. Plugin packages demonstrating those surfaces are installed separately; none ship with core.

Shipped in SDK 2.1

Connections, actions and forms, integration identities, maps and section refresh, typed slot context and the sandbox workflow are shipped. Plugin routes have been available since SDK v2.