v2.2.0 - ask searches

This release adds ask using withAsk() in GraphQL "Get" and "Explore"

v2.1.0 - nearObject searches

This release adds nearObject using withNearObject() in GraphQL "Get" and "Explore"

v2.0.0 - Support for Weaviate v1

This change contains breaking changes over previous version as it is aligned with the new API of Weaviate v1. Use the client version v2.0.0 and up for Weaviate instances running v1.0.0 and up. Use client version v1.1.x for Weaviate version 0.23.y.

Changes (and migration guide):

• .withKind() removed
  Due to the removal of semantic Kinds ("things/actions") in Weaviate, the .withKind() method is removed on all builders

• .withSchema() -> .withProperties()
  Due to the renaming of object.schema to object.properties in Weaviate, all .withSchema({"foo": "bar"}) methods were renamed to .withProperties({"foo": "bar"})

• .withInterpretation() => .withAdditional('interpretation') on Getter/GetterById
  This change reflects two changes in Weaviate: First up, "Underscore Properties" are now called "Additional Properties", furthermore the presence of such properties may depend on modules and is thus now dynamic. As such, the desired additional property is now passed in as a string.

  Note: There is one exception: .withVector() can still be used, as the field vector has been "upgraded" from an underscore/additional property to a regular property

• .withExplore() -> .withNearText()
  Following the renaming of explore to nearText in Weaviate the builder method was renamed accordingly. Additionally, the new method .withNearVector({vector: [...]}) was introduced to allow for nearVector searches.

  Note: GraphQL Explore { } queries in Weaviate v1 were changed to no longer be specific to text searches. As a result the client builder methods .withConcepts(), .withMoveTo() and .withMoveAwayFrom() were replaced with .withNearText({concepts: [...], ...}). Similarly to GraphQL Get { }, the new method .withNearVector({vector: [...]})

• .withK(3) -> .withSettings({k: 3}) in classification builder
  To reflect the API changes in the classification builder the kNN-specific method .withK(), was replaced with a more generic .withSettings({}) which takes any classification type-specific settings, such as {k: 3} for kNN or {tfidfCutoffPercentile: 80} for text2vec-contextual

v1.1.2 - Bundle and release code

This release introduces a better build pipeline where the code is bundled and transpiled. This transforms ES6-specific features and experimental features into widely supported ES5 code. As a result, the weaviate-client package should now be usable from many dev setups, including "Create React App" without requiring further changes.

In addition this contains fixes over the two previous failed releases:

• v1.1.1: Issue where the build pipeline didn't include the artifact
• v1.1.0: Issue where the default export was missing

v1.1.1 - do not use, use v1.1.2 instead

Skip this release, use v1.1.2 instead.

v1.1.0 - do not use, use v1.1.2 instead

Skip this release, use v1.1.2 instead, it contained a broken export.

v1.0.0 - Weaviate API feature completion

This release marks the point where the Javascript client can be considered feature-complete. It contains methods for all API endpoints in Weaviate 0.22.16 - the latest Weaviate release at the time of this release.

See the documentation for details on how to use the client