Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

Client should expose received controls for non-search actions #192

Closed
pfmooney opened this issue May 24, 2014 · 1 comment
Closed

Client should expose received controls for non-search actions #192

pfmooney opened this issue May 24, 2014 · 1 comment
Assignees
Milestone

Comments

@pfmooney
Copy link
Contributor

It appears that only client.search exposes received message controls via the EventEmitter during searchResult parsing. Some other actions (see #186) would benefit from access to control information at the time of callback.

@pfmooney pfmooney added this to the 0.8.0 milestone May 24, 2014
@pfmooney pfmooney self-assigned this May 24, 2014
@pfmooney pfmooney modified the milestones: 0.8.0, 1.1.0 Oct 23, 2015
@jsumners
Copy link
Member

👋

On February 22, 2023, we released version 3 of this library. As a result, we are closing this issue/pull request.

Please see issue #839 for more information, including how to proceed if you feel this closure is in error.

@ldapjs ldapjs locked as resolved and limited conversation to collaborators Feb 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants