Skip to content

Releases: sanity-io/sanity-algolia

1.1.0

06 Mar 19:28
6d655e1
Compare
Choose a tag to compare

Whats changed

  • No longer dependent on @sanity/client and you should be able to pass in any version of that library to this function.
  • Possibly fewer delete operations made in Algolia API after a logic change
  • Added example of using this module with Netlify functions

Changelog

  • Handle async SerializeFunction by @runeb in #15
  • Update README.md by @afflexux in #18
  • Clean up type dependency and imports by @runeb in #20
  • Revert "Clean up type dependency and imports" by @runeb in #21
  • Update README.md by @jleknes in #22
  • fix: Remove dependency, add examples by @runeb in #36
  • Export TypeConfig and IndexMap by @hyldmo in #35
  • Fixed multiple delete calls for the same index by @stbychkov in #24

New Contributors

Full Changelog: 1.0.2...1.1.0

1.1.0-alpha

30 Jun 20:04
Compare
Choose a tag to compare
1.1.0-alpha Pre-release
Pre-release

A preview release of new features for async serialization and indexing multiple Algolia records for a single Sanity document. More details in pull request #14

1.0.2

16 Apr 20:25
28e256f
Compare
Choose a tag to compare

Optimize GROQ query performance by using two in operators as opposed to adding arrays

1.0.1

15 Mar 16:47
6d7c9b8
Compare
Choose a tag to compare

Small patch release to include a safety check on rich text node having text before flattening.
No API change.

1.0.0

13 Feb 23:14
bf9f02b
Compare
Choose a tag to compare

Version 1.0.0 brings some requested flexibility in how Sanity documents are fetched before you map them to Algolia records. It is now easy to resolve references. See the updated example in README.

Note that updating will require that you update your code slightly.

Before

  const sanityAlgolia = indexer(
    {
      post: algoliaIndex
    },
    

After

  const sanityAlgolia = indexer(
    {
      post: {index: algoliaIndex}
    },
    

0.3.0

13 Feb 21:55
d8b0a06
Compare
Choose a tag to compare

Added feature to guard against querying the datastore before some indexes have been updated. This will cause your webhook handler to run for 2 extra seconds. If you have implemented your own sleep/delay you may remove this after updating.