-
Notifications
You must be signed in to change notification settings - Fork 127
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
Fix repeated build-nested-set warning (#1634) #1682
Fix repeated build-nested-set warning (#1634) #1682
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some comments on a couple of minor issues, but otherwise this works as expected! Thanks @phalene-bytes!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, another minor nitpick! — the commit message header should be 50 characters max, and we usually have the issue number in the brackets at the end (this helps with GitHub's issue linking). I'd suggest amending the commit message to be less than 50 characters, and using the commit message body (72 characters per line) if you need more than 50 characters.
3f9541b
to
84f99db
Compare
84f99db
to
f4fa981
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Removes "Note: you will need to rebuild your search index for updates to show up properly in search results." out of recursivelyUpdateTree() function