Petar Španja

Implement support for ranges

1

Ranges can be implemented as an extension with a custom Term token, but it would still be nice to have them in the base syntax. The way [Elasticsearch defines them](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#_ranges)...

Basically same as `/api/bookmarks/` now works, but with information about available and selected tags for the search. Something like: ```json { "count": 123, "next": "http://127.0.0.1:8000/api/bookmarks/?limit=100&offset=100&q=example", "previous": null, "results": [ {...

`FieldType::fromHash()` should return an instance of field type's value, but instead it returns an instance of `InputValue`. That means it will not work correctly over REST API.

Hi, not sure if making omnibox keyword configurable is possible with Firefox, but it would be nice to have.