v2.35.1 The Real 2.35!

Didn't actually compile the javascript when we cut 2.35.0, so use this one!

• redo release 55e68fb

v2.35.0...v2.35.1

# 2.35.0 (2025-07-22)

2.35.0 (2025-07-22)

• Document Resolver (i.e look up a doc by id) didn't pick up the basic auth credentials, unlike the Searcher.
  Shows up in Quepid as Snapshot compare failing. Thanks @kiratraynor for identifying the bug and pairing on the fix. #153 by @epugh.

• Make sure the Resolver picks up the basic auth credentials (#153) fbd5481

v2.34.0...v2.35.0

# 2.34.0 (2025-02-28)

• Smarter handling of basic auth, especially when you have special characters like $ and @ in the password.
  For all api methods except JSONP, we use the Authorization header, even if you pass in a url with the embedded basic auth like http://user:pass@myserver.com.
  Then for JSONP, which does NOT support headers, we embed the basic auth back into the URL.
  FYI: Chrome does NOT allow you to use embedded username password in the URL.
  Thanks @atarora for opening o19s/quepid#1245 and @david-fisher for isolating the root causes.

• Match next release version bb989a8

• Smarter handling of Basic Auth and encoded characters. (#152) d68e77b

---

v2.33.0...v2.34.0

2.32.0 - Algolia Support!

2.32.0 (2024-02-07)

• Algolia support added! Thanks @sumitsarker for the great contribution, #145.

v2.32.0...v2.33.0

# 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.

v2.31.0...v2.32.0

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 with SUSS_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.7 (2023-12-05)

• Support Custom Headers being passed through to Solr. We have a nice refactoring of how headers are processed, and reusing the esUrlSvc in the solrSearcherFactory. #143 by @epugh.

v2.30.6...v2.30.7

# 2.30.6 (2023-11-30)

2.30.6 (2023-11-30)

• It appears that the DocResolver is needed regardless of if you support it or not. Weird stuff in Quepid otherwise happens. #141 by @epugh rolls back the change.

v2.30.5...v2.30.6

# 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.

v2.30.4...v2.30.5

# 2.30.4 (2023-11-27)

2.30.4 (2023-11-27)

• Custom Headers can now be used with Search API's. #138 by @dacox. Thanks Doug Cox!

v2.30.3...v2.30.4