improve set_value error message.

[suketa]

Summary by CodeRabbit

• Bug Fixes
  • Improved error message for unsupported data types to include the actual value being processed, making debugging clearer without changing behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fcfa324d-900f-4d0e-bc87-e79dc855128f

📥 Commits

Reviewing files that changed from the base of the PR and between 83d3be9 and 8734794.

📒 Files selected for processing (1)

• lib/duckdb/data_chunk.rb

🚧 Files skipped from review as they are similar to previous changes (1)

• lib/duckdb/data_chunk.rb

---

📝 Walkthrough

Walkthrough

Changed the error message in DataChunk#set_value to include the inspected value alongside the type_id for unsupported types. No control flow, NULL handling, exported/public declarations, or other logic were modified.

Changes

Cohort / File(s)	Summary
Error Message Change lib/duckdb/data_chunk.rb	Adjusted the Unsupported type for DataChunk#set_value message to: includes #{value.inspect} with the type_id. No functional behavior altered.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add DataChunk#set_value for high-level value writing #1107 — Prior change also touched DataChunk#set_value; this PR modifies the unsupported-type error message introduced/affected by that change.

Poem

🐇 I nibbled on code, then gave a sigh,

The message now shows the value nearby.
Tiny change, but clear and spry,
Debugging hops along — oh my! 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'improve set_value error message' directly and accurately describes the main change: enhancing the error message in the set_value method by including the actual value being processed.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch improve_set_value_error_message

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@lib/duckdb/data_chunk.rb`:
- Line 104: The error message in DataChunk#set_value is missing a space before
the backtick; update the raise ArgumentError string in the set_value
implementation to insert a space between "value" and the backtick so it reads
"for value `#{value.inspect}`" (preserve the rest of the message and
interpolation including type_id).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1e2d67f1-397f-4990-ae82-e1a662389ed0

📥 Commits

Reviewing files that changed from the base of the PR and between 60b20f0 and 83d3be9.

📒 Files selected for processing (1)

• lib/duckdb/data_chunk.rb