feat: WASM serverEvents capability with generic event mechanism #2295
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove eslint-disable directives for no-explicit-any and replace generic any types with proper TypeScript interfaces throughout the WASM subsystem. Changes: - Add SignalKApp interface for type-safe app object access - Add WasmRawExports interface for WASM module exports - Add WasmDelta, WasmCapabilities, and related interfaces - Replace any with Record<string, unknown> for dynamic objects - Replace any with unknown for truly unknown values - Remove unused variables and imports - Add proper type imports across binding files
dirkwa
force-pushed
the
feature/wasm-strict-and-events
branch
2 times, most recently
from
408bf0e to
3692ed5
Compare
Enable WASM plugins to subscribe to server events and emit custom plugin events via FFI bindings: - sk_subscribe_events: subscribe to specific event types - sk_emit_event: emit PLUGIN_* prefixed events - sk_get_allowed_event_types: query available event types Add WasmEventManager for subscription filtering, buffering during plugin startup, and event routing. Add example-event-handler-rust demonstrating server statistics monitoring with HIGH_DELTA_RATE alert emission.
dirkwa
force-pushed
the
feature/wasm-strict-and-events
branch
from
3692ed5 to
933cf5a
Compare
Member
|
I am afraid this is still addressing just serverevents and not the generic event mechanism documented a bit at https://github.com/SignalK/signalk-server/wiki/Events-and-Outputting-Data. See also 6768da9. A good idea for demo wasm plugin event handling would be something that listens for for example nmea0183 data and emits nmea2000 |
Enable WASM plugins to subscribe to and emit NMEA data stream events
(nmea0183, nmea2000JsonOut, etc.) in addition to server events.
- Add nmea0183, nmea0183out, nmea2000JsonOut, nmea2000out,
nmea2000OutAvailable, and canboatjs:* to allowed event types
- Subscribe plugins to generic events via app.on() lifecycle
- Allow sk_emit_event to emit standard event names without PLUGIN_ prefix
- Fix missing serverEvents capability loading from package.json
- Add unit tests for event manager
- Document serverEvents capability in capabilities.md
Generic events are emitted directly to the server bus for interop with
other plugins and the Signal K data pipeline. Custom plugin events
still receive PLUGIN_ prefix for security.
Example plugin demonstrates NMEA 0183 to NMEA 2000 PGN conversion.
dirkwa
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Completes the serverEvents capability for WASM plugins, enabling them to receive both
server events and NMEA data stream events, and emit events back to the Signal K pipeline.
Changes
Generic event mechanism:
canboatjs:* to allowed event types
TypeScript strict mode:
Documentation:
Testing
129025/129026)