Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

splainer-search

Package Overview
Dependencies
Maintainers
3
Versions
78
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

splainer-search - npm Package Versions

23
8

2.33.0

Diff

epugh
published 2.32.0 •

Changelog

Source

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. https://github.com/o19s/splainer-search/pull/148 by @epugh.
epugh
published 2.31.0 •

Changelog

Source

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. https://github.com/o19s/splainer-search/pull/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 https://github.com/o19s/quepid/issues/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. https://github.com/o19s/splainer-search/pull/147 by @epugh.

epugh
published 2.30.7 •

Changelog

Source

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. https://github.com/o19s/splainer-search/pull/143 by @epugh.
epugh
published 2.30.6 •

Changelog

Source

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. https://github.com/o19s/splainer-search/pull/141 by @epugh rolls back the change. Thanks @dacox for https://github.com/o19s/splainer-search/issues/140.
epugh
published 2.30.5 •

Changelog

Source

2.30.5 (2023-11-29)

  • 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! https://github.com/o19s/splainer-search/pull/139 by @epugh. Thanks @david-fisher for finding the snapshot with proxies issue.
epugh
published 2.30.4 •

Changelog

Source

2.30.4 (2023-11-27)

  • Custom Headers can now be used with Search API's. https://github.com/o19s/splainer-search/pull/138 by @dacox. Thanks Doug Cox!
epugh
published 2.30.3 •

Changelog

Source

2.30.3 (2023-11-16)

  • Bug fix for arrays passed into query templating via qOptions. https://github.com/o19s/splainer-search/pull/137 by @mkr.
  • Avoid the query object -> string -> hydrating -> string -> query object roundtrip and directly hydrate on the query object. https://github.com/o19s/splainer-search/pull/136 by @mkr.
epugh
published 2.30.2 •

epugh
published 2.30.1 •

23
8
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc