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
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -521,9 +521,21 @@ When the `handler` function is invoked, it will be passed an object with the fol
521
521
*`method` {String} - The name of the method being invoked (useful for wildcard handlers).
522
522
*`params` {*} - The `params` value passed to the call.
523
523
*`signal` {AbortSignal} - A signal which will abort if the underlying connection is dropped (therefore, the response will never be received by the caller). You may choose whether to ignore the signal or not, but it could save you some time if you use it to abort the call early.
524
+
*`messageId` {String} - The OCPP Message ID used in the call.
524
525
525
526
If the invocation of the `handler` resolves or returns, the resolved value will be returned to the caller.
526
527
If the invocation of the `handler` rejects or throws, an error will be passed to the caller. By default, the error will be an instance of `RPCGenericError`, although additional error types are possible ([see createRPCError](#createrpcerrortype-message-details)).
528
+
If the `handler` returns a `NOREPLY` symbol then no reply will be sent. It will be your responsibility to send the reply by some other means (such as [`sendRaw()`](#clientsendrawmessage)).
0 commit comments