Samyak S Sarnayak 30247d70cd Fix search highlight for non-unicode chars ... The `matching_bytes` function takes a `&Token` now and: - gets the number of bytes to highlight (unchanged). - uses `Token.num_graphemes_from_bytes` to get the number of grapheme clusters to highlight. In essence, the `matching_bytes` function returns the number of matching grapheme clusters instead of bytes. Should this function be renamed then? Added proper highlighting in the HTTP UI: - requires dependency on `unicode-segmentation` to extract grapheme clusters from tokens - `<mark>` tag is put around only the matched part - before this change, the entire word was highlighted even if only a part of it matched		2022-01-17 11:37:44 +05:30
..
public	Stringify objects on dashboard to avoid [Object object]	2021-09-08 17:51:08 +02:00
src	Fix search highlight for non-unicode chars	2022-01-17 11:37:44 +05:30
templates	add a button to display or hide the facets	2021-03-31 16:18:53 +02:00
Cargo.toml	Fix search highlight for non-unicode chars	2022-01-17 11:37:44 +05:30