-
Notifications
You must be signed in to change notification settings - Fork 14
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
Uncaught TypeError in lunr.js #32
Comments
This happens when we have an empty note undeleted (so if you want to avoid this problem right now, remove empty notes). Thanks for reporting it. |
looks like that worked, thanks! |
Ah that was a hack to avoid the bug. I'll reopen the issue and fix it in a right way. Thanks! |
When "Enable Lunr Pipeline" is off, and when the body is empty, the error occurs. lunr.js. this._fields.forEach(function (field) {
var fieldTokens = this.pipeline.run(lunr.tokenizer(doc[field.name]))
console.log(fieldTokens); // when body is empty, it gives [""], not [].
docTokens[field.name] = fieldTokens
lunr.SortedSet.prototype.add.apply(allDocumentTokens, fieldTokens)
}, this) |
#44 Duplicated. |
seongjaelee
added a commit
to seongjaelee/docquery
that referenced
this issue
Apr 22, 2016
Lower version is causing nvatom unusable: seongjaelee/nvatom#32 The bug fix is here: olivernn/lunr.js#178
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This errors pops up when searching regardless of whether "Enable Lunr Pipeline" is on.
Atom Version: 1.0.13
System: Mac OS X 10.10.5
Thrown From: nvatom package, v0.8.1
Stack Trace
Uncaught TypeError: Cannot read property 'tf' of undefined
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: