typesense

Hey, one thing i would like to suggest is better handling of non-complient documents trying to add to an collection. For example: when developing and migrating a existing data that has some weird permutations on some fields - it would be helpful if typesense wouldn’t just respond with “Invalid field ‘foobar’” (i’m quoting the error from my head) but with something like “Invalid field ‘foobar’ for document $documentId: expected “string”, got array (value: [‘foo1’, ‘foo2’])“.

even more awesome would be if:
a) there would then also be a way to get this specific data as properties of the requestmalformed exception in the php client and maybe even
b) if it would be possible to accept the document but have it not indexed (not sure how good this suggestion really is :D)

That would have helped me a lot in the initial development because right now i have to explicit catch the exception and then also log the complete document to retroactively figure out which documents failed and why.

<@U03EBJKMT39> These are good suggestions. Could you open a Github issue to document these?