fix typo.

[suketa]

fix typo. apend_int16 -> append_int16

Summary by CodeRabbit

• Bug Fixes
  • Corrected a typo in the method name for appending 16-bit integers in the DuckDB Appender implementation.

[coderabbitai]

Walkthrough

The pull request addresses a typographical error in the DuckDB Ruby extension's appender functionality. Specifically, the function name for appending a 16-bit integer was corrected from appender__apend_int16 to appender__append_int16. This change ensures the correct method naming and referencing within the Ruby DuckDB Appender class, maintaining the existing code structure and functionality.

Changes

File	Change Summary
ext/duckdb/appender.c	Corrected function name from appender__apend_int16 to appender__append_int16 in both function declaration and method binding

Possibly related PRs

• fix error message of appender_int64 #868: Similar function name correction for appender_append_int64 to appender__append_int64, indicating a pattern of fixing appender function naming

Poem

🐰 A typo hopped into our code today,
With "apend" instead of "append" gone astray,
A tiny fix, a character's dance,
Bringing precision with just one glance,
Ruby and DuckDB now sing in sync, hooray! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 297adfa and 3d0e896.

📒 Files selected for processing (1)

• ext/duckdb/appender.c (3 hunks)

✅ Files skipped from review due to trivial changes (1)

• ext/duckdb/appender.c

⏰ Context from checks skipped due to timeout of 90000ms (14)

• GitHub Check: test (head, 1.0.0)
• GitHub Check: test (3.4.1, 1.0.0)
• GitHub Check: test (3.4.1, 1.1.1)
• GitHub Check: test (3.4.1, 1.0.0)
• GitHub Check: test (3.4.1, 1.1.3)
• GitHub Check: test (3.3.6, 1.0.0)
• GitHub Check: test (3.3.6, 1.1.1)
• GitHub Check: test (3.3.6, 1.1.3)
• GitHub Check: test (3.3.6, 1.1.1)
• GitHub Check: test (3.3.6, 1.1.3)
• GitHub Check: test (3.2.6, 1.0.0)
• GitHub Check: test (3.2.6, 1.1.1)
• GitHub Check: test (3.2.6, 1.1.3)
• GitHub Check: test (3.1.6, 1.1.3)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.