|
|
@@ -42,7 +42,7 @@ rpclibrary offers a special type of call that can be used with callbacks. The ca
|
|
42
|
42
|
|
|
43
|
43
|
In order to function, some metadata has to be included in the return value of hooks. On success, the function is expected to return a `type SubscriptionResponse = { result: 'Success', uuid: string }` or in case of errors a `type ErrorResponse = { result: 'Error' }`.
|
|
44
|
44
|
|
|
45
|
|
-The uuid, as the name implies, is used to uniquely identify the callback for a given invocation and also dictates the name given to the client-side RPC. Unless you got a preferred way of generating these (e.g. using some kind of unique information important to your task) we reccomend [uuid](https://www.npmjs.com/package/uuid) for this purpose.
|
|
|
45
|
+The uuid, as the name implies, is used to uniquely identify the callback for a given invocation and also dictates the name given to the client-side RPC. Unless you got a preferred way of generating these (e.g. using some kind of unique information important to your task) we recommend [uuid](https://www.npmjs.com/package/uuid) for this purpose.
|
|
46
|
46
|
|
|
47
|
47
|
You should unhook the client socket once you're done with it as not to cause security or program flow issues.
|
|
48
|
48
|
|
