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

skip attribute with empty name#4

Merged
jsumners merged 3 commits intoldapjs:masterfrom
ahaenggli:master
Apr 21, 2023
Merged

skip attribute with empty name#4
jsumners merged 3 commits intoldapjs:masterfrom
ahaenggli:master

Conversation

@ahaenggli
Copy link
Copy Markdown
Contributor

This should resolve #867.

The search-request.js file has been changed so that empty attribute names are skipped while a corresponding warning is emitted.

Copy link
Copy Markdown
Member

@jsumners jsumners left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is fantastic. I get the impression it wasn't too difficult to figure any of the details and get them implemented.

Thinking a bit more about this, I think it would be better to make this warning fire each time an empty attribute type is attempted. The single warning is likely to get lost in the noise, and we want people to be aware of the missing data. What do you think?

In order to accomplish that, we need to bump the minimum version of process-warning in the dependencies list and apply the suggested change.

Comment thread lib/deprecations.js Outdated
@jsumners
Copy link
Copy Markdown
Member

@ahaenggli do you have any thoughts on the PR review?

@ahaenggli
Copy link
Copy Markdown
Contributor Author

I agree that making the warning fire each time an empty attribute type is attempted is a really good idea. This will make it easier to identify the affected clients and potentially fix any related queries.

@jsumners jsumners merged commit 0fbacd8 into ldapjs:master Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v3 server parser error with empty attribute name

2 participants