add cacheSearchTerm option

[crystalline]

Add cacheSearchTerm option (defaults to true, the same behavior as before) to mitigate #168

To fix the issue set cacheSearchTerm attribute of the ng2-completer to true.

Also add index.ts file, so ng2-completer could be installed from github like this: "yarn add yarn add https://github.com/oferh/ng2-completer

[oferh]

thanks for the PR.

there is already an index.ts under src

[crystalline]

Top-level index.ts is a copy of src one, with "src/" added to all import paths
Without this top-level index.ts it isn't possible to simply install the ng2-completer from the github via yarn or npm (it is possible if you edit your source to import from ng2-completer/src instead of ng2-completer).
If you don't like it you could remove it, but then I'd have to use my fork where there is ./index.ts .

[oferh]

can you split it to 2 PR's?
I think that changing typings path in package.json should be the solution for the location of index.ts.

[crystalline]

Ok, removed index.ts for now (but left that commit unchanged because I already depend on it in my project), will do something about index.ts or typings in the next PR

[oferh]

can you change it so that CompleterData can pass a resetDataSource flag that will trigger the term reset?

[oferh]

what was the issue here?

[oferh]

version 1.5.4 now includes dataSourceChange event in CompleterData when it is emitted CtrList will clear the cached term.

[marciomsm]

@oferh do you know when this PR will be merged? I am using cacheSearchTerm in my fork, but I am waiting to revert to your repository as a dependency in my project. Thanks.