understand that null responses can be returned for the key/value array #2814
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.
in #2772 users noted that we are throwing a javascript exception as we are trying to apply .length to a null and hence that fails.
we have 2 options. First, we can just elide these results from the response we give the user, but this wouldn't correspond to the ft.search documentation. Therefore, instead, as redis doesn't return a document, but a null, we should do the same, and return an empty null object for these documents. It's up to the user to handle them
fixes #2772
Description
Checklist
npm test
pass with this change (including linting)?