mirror of
https://github.com/nextapps-de/flexsearch.git
synced 2025-08-21 13:21:39 +02:00
fix typo in documentation #380
This commit is contained in:
@@ -359,7 +359,7 @@ index.append(1, "index appended content");
|
||||
|
||||
When you query `index.search("index")` then you will get index id 1 as the first entry in the result, because the context starts from zero for the appended data (isn't stacked to the old context) and here "index" is the first term.
|
||||
|
||||
If you didn't want this behavior than just ust `index.add(id, content)` and provide the full length of content.
|
||||
If you didn't want this behavior then just ust `index.add(id, content)` and provide the full length of content.
|
||||
|
||||
#### Check existence of already indexed IDs
|
||||
|
||||
@@ -1235,7 +1235,7 @@ index.export(function(key, data){
|
||||
});
|
||||
```
|
||||
|
||||
Exporting data to the localStorage isn't really a good practice, but if size is not a concern than use it if you like. The export primarily exists for the usage in Node.js or to store indexes you want to delegate from a server to the client.
|
||||
Exporting data to the localStorage isn't really a good practice, but if size is not a concern then use it if you like. The export primarily exists for the usage in Node.js or to store indexes you want to delegate from a server to the client.
|
||||
|
||||
> The size of the export corresponds to the memory consumption of the library. To reduce export size you have to use a configuration which has less memory footprint (use the table at the bottom to get information about configs and its memory allocation).
|
||||
|
||||
|
Reference in New Issue
Block a user