Releases: o19s/splainer-search
2.32.0 - Algolia Support!
2.32.0 (2024-02-07)
- Algolia support added! Thanks @sumitsarker for the great contribution, #145.
# 2.32.0 (2024-02-06)
2.32.0 (2024-02-06)
- Splainer lets you do smart things around using highlighting in the query and/or snippeting to 200 characters to take a really large document field and shrink it to something that renders nicely. However sometimes you just want to see ALL the text. So now in a field specification you can control that by specifing
unabridged:body_content
for your long form text fields. #148 by @epugh.
2.31.0
2.31.0 (2024-02-05)
-
When using Solr and proxing through Quepid, we require you to use a GET. However, when doing a doc lookup (to power snapshot compare) it falls back to JSONP, instead of using the specified GET. #146 by @epugh.
-
POTENTIALLY BREAKING CHANGE! Splainer-search has some logic around escaping queries. For example
OR
becomes\\OR
... It is rather unclear if this is actually a fully baked set of logic, and has created some bugs like o19s/quepid#910. We've commented out the escaping in Splainer-search, added logging about it, but will leave the code, tagged withSUSS_USE_OF_ESCAPING
. Going to ship this in the next version of Quepid and get feedback from community on if there are regressions that warrant restoring some sort of escaping. #147 by @epugh.
v2.30.7...v2.31.0
2.30.7 (2023-12-05)
# 2.30.6 (2023-11-30)
# 2.30.5 (2023-11-29)
2.30.5 (2023-11-29)
The changes (and fixes!) keep coming!
- Looking up individual documents from the search engine (i.e the DocResolver) didn't respect the proxy settings. Also found a bug in creating direct link to OpenSearch docs where you could get doubled
/_doc/_doc/
in the url! #139 by @epugh. Thanks @david-fisher for finding the snapshot with proxies issue.