No, keep those in the `template: {}` object like you have them, I'm just saying let's move the `resultsItem` outside of that block. It's a required field, so should be higher up. Something like this:
```
el: "",
listItem: "<li class='autocomplete__results__item' data-company='{{Company}}'>{{Company}}</li>",
template: {
  elementWrapper:  ...
  resultsWrapper: ...
  ...
}
```
Does that make sense? That way the user can entirely ignore the "template" config option when instantiating if they don't need/care about custom css classes and elements. We'll just use the defaults. Just trying to separate *optional* from *required* when instantiating.