Fanis Tharropoulos

```sh #!/bin/bash HOST="${TYPESENSE_HOST:-localhost:8108}" API_KEY="${TYPESENSE_API_KEY:-xyz}" COLLECTION="test_bug_fixed" echo "Testing include_fields bug fix..." echo "Host: $HOST" echo "" curl -s -X DELETE "http://$HOST/collections/$COLLECTION" -H "X-TYPESENSE-API-KEY: $API_KEY" > /dev/null curl -s -X POST "http://$HOST/collections"...

@rscotten The `photos` object is not defined in the collection's schema. If you intend to not index it and just store on disk, you can set `index: false`, which will...

The validation error still happens even if you send something like: ```py { "id": "1", "state": {"name": "somename", "documentId": "sdmdmd"}, "tags.name": ["name1", "name2"], "tags.documentId": ["doc1", "doc2"], "tags.slug": ["slug1", "slug2"], }...

Thanks for the snippet. Could you post a reproducible example like [this](https://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b) one? We want to eliminate any implementation-specific details to see if it's something that's caused by the server.

If you try to access it directly, if it doesn't exist, the client will instantiate a new object for it, so it is working as designed. May I know the...

It comes up often with users using the local in-memory instance about collections / analytics rules etc to access remote, real Typesense entities, leading to confusion. If you want to...

The issue in the original post is that the in-memory object will instantiate the children objects whether or not they exist in the remote Typesense instance. They don't directly call...

Hey Jonathan, Curation changes have bee merged and are available in our [latest release](https://github.com/typesense/typesense-php/releases/tag/v5.2.0)

addresseed both in #97

Implement #121