Tommy Smith

I'm happy to announce that this is fixed in the next major release! It's currently in an open community _beta_ and installable using `npm install weaviate-client --tag beta`. I will...

@dandv, this seems to be a multi-faceted issue. The core problem you're seeing is that the `learn-weaviate` API key in fact lacks the permissions necessary to use the `.checker()` method...

Hi @Kostjanix2, to help diagnose the issue could you please also post the class schema? Cheers 😁

Hi both @amirhouieh and @ElvinD, can the issue that you're both observing be summarised as so: - You have classes that depend on one another through their property definitions -...

Hi @iSuslov 😁 what is the status of this PR? Are you in a position to reply to https://github.com/weaviate/typescript-client/pull/56#issuecomment-1545785442?

Hi @tritos-design, thanks for flagging this one! It's actually not intended that users provide the `host` parameter as `http://localhost` since this is a URL. This is why the client infers...

Hi @josiahbryan, thanks for raising this. I'll look into it and get back to you!

@josiahbryan, I have setup and installed fresh versions of your Node version and the latest client on my Windows and Mac machines without issue! The current CI tests the package's...

No, that's quite unexpected since such dependencies should be private and are not peer dependencies! I only ran `npm install weaviate-ts-client` in my empty `package.json` file without issues 🤔 My...

@Abhijithchintu, thanks for the contribution! https://github.com/weaviate/typescript-client/pull/81 is now merged, which covers warning for outdated Weaviate. Warning for an outdated client is still open, would you like to open a PR...