docs: correct the dead-output component count from 11 to 9
Counted from source: the 22 remaining outputs sit in 9 components, not 11. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -301,7 +301,7 @@ hydrated DOM, which already looks correct today.
|
||||
|
||||
### 3.1 Twenty-two outputs still have no emitter
|
||||
|
||||
**Issue.** 22 outputs across 11 components are declared and never fired:
|
||||
**Issue.** 22 outputs across 9 components are declared and never fired:
|
||||
FileUpload (upload, progress, success, cancel, remove), ToastNotifications (add,
|
||||
dismiss, clear, action), AdvancedDatePicker (open, close, clear),
|
||||
AdvancedRangeSlider (start, end), Chart (dataPointClick, legendToggle), Confetti
|
||||
|
||||
@@ -2158,11 +2158,13 @@
|
||||
"PubSub",
|
||||
"PubSubDriver",
|
||||
"ResilientPubSubOptions",
|
||||
"SubjectPubSub",
|
||||
"createPubSub",
|
||||
"createResilientPubSub",
|
||||
"kafkaDriver",
|
||||
"memoryDriver",
|
||||
"natsDriver"
|
||||
"natsDriver",
|
||||
"subjectPubSub"
|
||||
],
|
||||
"./brokers": [
|
||||
"KafkaClient",
|
||||
@@ -2224,6 +2226,8 @@
|
||||
"RedisQueueClient",
|
||||
"ScheduledJob",
|
||||
"SqlQueueClient",
|
||||
"SubjectJob",
|
||||
"SubjectQueue",
|
||||
"WorkflowDefinition",
|
||||
"WorkflowEngine",
|
||||
"WorkflowRunContext",
|
||||
@@ -2246,7 +2250,8 @@
|
||||
"queueDashboardSnapshot",
|
||||
"redisQueueStore",
|
||||
"renderQueueDashboard",
|
||||
"runQueueDaemon"
|
||||
"runQueueDaemon",
|
||||
"subjectQueue"
|
||||
]
|
||||
},
|
||||
"@wrnexus/reactive": {
|
||||
@@ -2392,6 +2397,8 @@
|
||||
"RPC_IDENTITY_HEADER",
|
||||
"RPC_INTERNAL_HEADER",
|
||||
"RPC_PATH_PREFIX",
|
||||
"RPC_STREAM_PATH_PREFIX",
|
||||
"RetryTransportOptions",
|
||||
"RpcErrorCode",
|
||||
"RpcTarget",
|
||||
"ServiceClient",
|
||||
@@ -2401,6 +2408,11 @@
|
||||
"ServiceHandlers",
|
||||
"ServiceImplementation",
|
||||
"ServiceResult",
|
||||
"StreamClient",
|
||||
"StreamClientOptions",
|
||||
"StreamHandlers",
|
||||
"StreamImplementOptions",
|
||||
"StreamImplementation",
|
||||
"SubjectContext",
|
||||
"ToResultOptions",
|
||||
"Transport",
|
||||
@@ -2409,14 +2421,18 @@
|
||||
"failure",
|
||||
"httpTransport",
|
||||
"implement",
|
||||
"implementStream",
|
||||
"importSubjectContext",
|
||||
"inProcessTransport",
|
||||
"isRetryableStatus",
|
||||
"procedure",
|
||||
"resolveAppOrigin",
|
||||
"retryingTransport",
|
||||
"rpcPath",
|
||||
"rpcSecret",
|
||||
"rpcStreamPath",
|
||||
"serviceClient",
|
||||
"streamClient",
|
||||
"success"
|
||||
]
|
||||
},
|
||||
|
||||
@@ -62,7 +62,7 @@ component.
|
||||
|
||||
## Outstanding, with numbers
|
||||
|
||||
**22 outputs across 11 components have no emitter of any kind** (was 32 across
|
||||
**22 outputs across 9 components have no emitter of any kind** (was 32 across
|
||||
16; see the correction above). The component advertises an output, a caller
|
||||
binds to it, and nothing ever fires. Native event names are excluded — the
|
||||
runtime binds a DOM-listener fallback on component tags, so `click` and `input`
|
||||
|
||||
Reference in New Issue
Block a user