Rob Hoelz

Hi @StarfallProjects! Just to make sure I understand your issue - does [this fiddle](https://jsfiddle.net/73Lch295/1/) demonstrate the behavior you're seeing? If not, could you provide a small fiddle that does?

Ok, thanks! I guess I'm kind of confused about the need to pad every search with wildcards - if it's a matter of not finding `someFunctionName(param)`, I recommend changing the...

Regarding the wildcard behavior you saw, I think that stemming is indeed the culprit here - if you inspect the index object in the fiddle, there are three terms in...

@giuliac89 FWIW, you could add this feature in current lunr.js by tweaking the pipeline - I believe the forced lowercasing that currently happens happens in the tokenizer.

@olivernn Hi there, and thanks for all your hard work on lunr.js! I wanted to chime in with my use case for mutable indexes - I wrote a TiddlyWiki plugin...

If anyone's interested, I started a PR (https://github.com/olivernn/lunr.js/pull/315) adding a `lunr.MutableBuilder` and `lunr.MutableIndex` type for, well, mutable indexes. I'm going to be using them for my plugin, and feedback on...

@taxidriver61 @abastardi You might also want to check out my lunr extension, [lunr-mutable-indexes](https://www.npmjs.com/package/lunr-mutable-indexes), which adds mutable index support to 2.x!

@sosharma1403 One way to fix this would be to add `lunr.trimmer` to `this.searchPipeline` in the `lunr` function invocation. @olivernn Do you think that would make sense to have in the...

@aecorredor I know next to nothing about React Native, so bear with me, but how are you passing the pre-built search index to search? Are you keeping it around in...

@aecorredor From the look of that error message, I'm guessing that's the issue