Skip to content

UN-2587 [FEAT] Add table processing mode support in LLM Whisperer connector#193

Merged
johnyrahul merged 1 commit intomainfrom
UN-2587-task-support-table-processing-mode-in-llm-whisperer-connector
Jul 14, 2025
Merged

UN-2587 [FEAT] Add table processing mode support in LLM Whisperer connector#193
johnyrahul merged 1 commit intomainfrom
UN-2587-task-support-table-processing-mode-in-llm-whisperer-connector

Conversation

@johnyrahul
Copy link
Contributor

Summary

  • Added support for "table" processing mode in LLM Whisperer v2 connector
  • Updated the JSON schema to include "table" as a valid processing mode option

Changes

  • Modified json_schema.json to add "table" to the enum of valid processing modes
  • This enables the LLM Whisperer connector to use the table processing mode for better table extraction

Test plan

  • Verify that the table processing mode is now available in the connector configuration
  • Test table extraction functionality with the new mode

🤖 Generated with Claude Code

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 11, 2025

Summary by CodeRabbit

  • New Features
    • Expanded available processing modes in the Text Extractor to include a new "table" option.

Walkthrough

The JSON schema for the LLMWhisperer v2 Text Extractor adapter was updated to allow the "mode" property to accept an additional value, "table", expanding the set of valid modes recognized by the schema.

Changes

File Change Summary
src/unstract/sdk/adapters/x2text/llm_whisperer_v2/src/static/json_schema.json Added "table" as an allowed value for "mode".

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to Reviews > Disable Cache setting
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 10044d3 and cff6c17.

📒 Files selected for processing (1)
  • src/unstract/sdk/adapters/x2text/llm_whisperer_v2/src/static/json_schema.json (1 hunks)

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

@johnyrahul johnyrahul changed the title UN-2587: Add table processing mode support in LLM Whisperer connector UN-2587 [FEAT] Add table processing mode support in LLM Whisperer connector Jul 11, 2025
@johnyrahul johnyrahul merged commit bbbbaaf into main Jul 14, 2025
2 checks passed
@johnyrahul johnyrahul deleted the UN-2587-task-support-table-processing-mode-in-llm-whisperer-connector branch July 14, 2025 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants