vsm-dictionary-cacher
Advanced tools
Comparing version 1.1.0 to 1.1.1
{ | ||
"name": "vsm-dictionary-cacher", | ||
"version": "1.1.0", | ||
"version": "1.1.1", | ||
"description": "Wrapper around a VSM-dictionary, that manages a cache of string-match results", | ||
@@ -5,0 +5,0 @@ "main": "src/VsmDictionaryCacher.js", |
@@ -150,10 +150,10 @@ # vsm-dictionary-cacher | ||
> A `vsm-autocomplete` needs a corresponding dictInfo for each of its | ||
> string-matches. | ||
> So if its string-matches already came from cache-hits, then the above | ||
> makes all its other data also come only from cache. | ||
> A `vsm-autocomplete` needs a corresponding dictInfo for each of its | ||
> string-matches. | ||
> So if its string-matches already came from cache-hits, then the above | ||
> makes all its other data also come only from cache. | ||
> If a `vsm-box` with a template, or several `vsm-box`es loaded on a same | ||
> page, would launch multiple concurrent requests for dictInfos, then this | ||
> cache process may result in a lot less queries to the underlying datastore. | ||
> If a `vsm-box` with a template, or several `vsm-box`es loaded on a same | ||
> page, would launch multiple concurrent requests for dictInfos, then this | ||
> caching may result in a lot less queries to the underlying datastore. | ||
@@ -187,2 +187,4 @@ <br> | ||
<br> | ||
## Options | ||
@@ -189,0 +191,0 @@ |
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
100382
236
0