This repository was archived by the owner on May 14, 2024. It is now read-only.
Allow single character attribute names #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves issue #2.
The
isValidAttributeStringfunction validates search attributes as defined in https://www.rfc-editor.org/rfc/rfc4511#section-4.5.1.8. In particular, the issue described is around theattributedescriptioncomponent defined by https://www.rfc-editor.org/rfc/rfc4512#section-2.5. Specifically anattributypeof theoidvariant.OIDs are described in https://www.rfc-editor.org/rfc/rfc4512#section-1.4 as being a
desc => keystring => leadkeychar *keychar. Withleadkeycharbeing anALPHAcharacter, andkeycharbeingALPHA,DIGIT, and/orHYPHEN.The miss here is that
*keycharmeans "zero or more keychars", not "one or more keychars".