From d6ffd550e93fb9889d0178aeece2d10a9355f357 Mon Sep 17 00:00:00 2001 From: link Date: Mon, 24 May 2021 13:33:09 +0800 Subject: [PATCH] Update docs/client.md Co-authored-by: Tony Brix --- docs/client.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/client.md b/docs/client.md index 60666f9..7ff9f37 100644 --- a/docs/client.md +++ b/docs/client.md @@ -279,7 +279,7 @@ containing the following fields: Responses inside callback of the `search` method are an `EventEmitter` where you will get a notification for each `searchEntry` that comes back from the server. You will additionally be able to listen for a `searchRequest` , `searchReference`, `error` and `end` event. -`searchRequest` is emitted immediately after every `SearchRequest` is sent with a `SearchRequest` param. You can do op +`searchRequest` is emitted immediately after every `SearchRequest` is sent with a `SearchRequest` parameter. You can do operations like `client.abandon` with `searchRequest.messageID` to abandon this search request. Note that the `error` event will only be for client/TCP errors, not LDAP error codes like the other APIs. You'll want to check the LDAP status code (likely for `0`) on the `end` event to assert success. LDAP search results can give you a lot of status codes, such as