Typesense package is missing types

[PatricioNG]

It seems like the latest version of the Typesense library, 3.0.1 is missing a key feature from Typesense 30.1, namely. Curation sets are not present in the library. Could this be added to the library as soon as possible?

[PatricioNG]

FYI @jasonbosco thanks for solving the NPM package a few weeks ago, it seems like there's still more work needed for this

[PatricioNG]

It also looks like the shape of analytics also doesn't align, the SDK suggests it is in a {rules: []} object but in reality it is not which is a breaking issue

[jamiezim4]

In particular, here is the problem we are having with curation sets, which is that overrides are an option but we can't link a curation set to an existing collection (operations around curation sets in isolation seem to be working just fine).

[tharropoulos]

Hey @jamiezim4 ,

.curationSets being accessible through collections aren't something that's outlined in the documentation. They're accessible through Client.curationSets(). You can find the linked curation sets of a collection by calling retrieve() and then use .curation_sets like so:

c.collections("global").retrieve().then((col) => col.curation_sets);

This was missed in the type definitions and added on #332

[tharropoulos]

@PatricioNG analytics access is fixed on #333

[PatricioNG]

Thanks! Looking forward to the release @tharropoulos

[jamiezim4]

@tharropoulos @jasonbosco
Do you know if enabling synonyms + stemming on a curation set rule is missing just on the typesense-js library or in the typesense API as well? Adding these settings when creating a curation rule via the API doesn't seem to take effect (or at least doesn't show in the response).

[PatricioNG]

@jasonbosco do we have a planned date for releasing those two fixes that got merged into master?

[tharropoulos]

Hey @jamiezim4,

What you're describing shouldn't be related to this issue or the client in general. Could you reach out to support@typesense.org with your cluster ID if you're on Typesense cloud or provide small reproducible example like this one so we can debug this issue locally if self-hosting?

[tharropoulos]

New release under 3.0.2. Could you try upgrading to that and see if your issue has been resolved?

[PatricioNG]

Thanks @tharropoulos this is solved now