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

Complete set union is not complete #469

Closed
bleroy opened this issue Jul 20, 2020 · 3 comments · Fixed by #470
Closed

Complete set union is not complete #469

bleroy opened this issue Jul 20, 2020 · 3 comments · Fixed by #470

Comments

@bleroy
Copy link
Contributor

bleroy commented Jul 20, 2020

A union with the complete set should be complete. Instead, the other set is returned. This hides another bug in search where clauseMatches is initialized with the complete set instead of the empty set.

bleroy added a commit to bleroy/lunr.js that referenced this issue Jul 20, 2020
olivernn pushed a commit that referenced this issue Aug 1, 2020
@olivernn
Copy link
Owner

olivernn commented Aug 1, 2020

Hey, thanks for the fix, I've merged it now. Before I cut a new release though I'd like to understand this:

This hides another bug in search where clauseMatches is initialized with the complete set instead of the empty set.

Are you saying that there is a bug now that the the union of a complete set is fixed? Was that included in your change, or is there still work to be done?

@bleroy
Copy link
Contributor Author

bleroy commented Aug 2, 2020

My fix is for both. It’s just that the second issue was hidden by the first one but both are fixed now.

@bleroy
Copy link
Contributor Author

bleroy commented Aug 2, 2020

Second issue is fixed by starting from an empty set in index.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants