Remove collection_name field when indexing or updating

[jaeyson]

Fixes #77

Summary by Sourcery

Ensure collection_name is not included in document data when indexing or updating, aligning with expected API behavior and preventing storage of extraneous fields.

Bug Fixes:

• Remove collection_name field from documents before indexing or updating to prevent unintended data storage.

Tests:

• Update tests to reflect removal of collection_name from indexed documents.

[sourcery-ai]

Reviewer's Guide

This PR ensures the 'collection_name' field is removed from document maps before indexing or updating, and updates related tests to match the new behavior.

File-Level Changes

Change	Details	Files
Remove 'collection_name' field from document bodies before indexing or updating.	Drop 'collection_name' (string or atom) from document map in index_document/4 before sending to API. Drop 'collection_name' (string or atom) from document map in update_document/4 before sending to API.	lib/ex_typesense/document.ex
Update tests to reflect removal of 'collection_name' from indexed document response.	Adjust test assertions to no longer expect 'collection_name' in response from index_document. Update get_document test to use original document's collection_name.	test/document_test.exs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#77	When updating a document via a map, the collection_name field should not be added to the document if it wasn't there before.	✅

Possibly linked issues

• Updating document from map adds collection_name field to document #77: The PR removes the collection_name field during document indexing and updating, which directly resolves the issue where this field was being added unexpectedly.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @jaeyson - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}