Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add complete API support for the LDAP connector #46

Merged
merged 20 commits into from
Jun 17, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add doc comments to enum types in SearchScope
  • Loading branch information
Nuvindu committed Jun 17, 2024
commit 90cdd7cc9dbb34bb79605b6b5494647466ebb11a
10 changes: 5 additions & 5 deletions ballerina/types.bal
Original file line number Diff line number Diff line change
Expand Up @@ -72,15 +72,15 @@ public type Control record {|
|};

# Scope of the search operation.
#
# BASE - Indicates that only the entry specified by the base DN should be considered. \
# ONE - Indicates that only entries that are immediate subordinates of the entry specified by the base DN (but not the base entry itself) should be considered. \
# SUB - Indicates that the base entry itself and any subordinate entries (to any depth) should be considered. \
# SUBORDINATE_SUBTREE - Indicates that any subordinate entries (to any depth) below the entry specified by the base DN should be considered, but the base entry itself should not be considered, as described in draft-sermersheim-ldap-subordinate-scope.
#
public enum SearchScope {
# Indicates that only the entry specified by the base DN should be considered
BASE,
# Indicates that only entries that are immediate subordinates of the entry specified by the base DN (but not the base entry itself) should be considered
ONE,
# Indicates that the base entry itself and any subordinate entries (to any depth) should be considered
SUB,
# Indicates that any subordinate entries (to any depth) below the entry specified by the base DN should be considered, but the base entry itself should not be considered, as described in draft-sermersheim-ldap-subordinate-scope
SUBORDINATE_SUBTREE
};

Expand Down