understand that null responses can be returned for the key/value array
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
Describe your pull request here
Checklist
- [ ] Does
npm testpass with this change (including linting)? - [ ] Is the new or changed code fully tested?
- [ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
is there any update on this? 👀
any update on this?
Closing this one as #2772 was fixed in #2988