No actionable comments were generated in the recent review. 🎉

Summary by CodeRabbit

• UI Improvements
  • Updated user-facing labels for the LLMWhisperer API key configuration field across adapters for clarity and consistency.

Walkthrough

Two JSON schema configuration files for the LLMWhisperer text extraction adapters update the user-facing display label for the unstract_key field from "Unstract Key" to "LLMWhisperer Key". The changes affect both the v1 and v2 adapter versions with identical edits to the schema field metadata.

Changes

Schema Field Label Updates

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

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.

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

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[JSON Schema\njson_schema.json] -->|parsed by| B[Adapter Config UI]
    B --> C[unstract_key field]
    C --> D["title: 'LLMWhisperer Key'\n(was: 'Unstract Key')"]
    C --> E["description:\n'API key from Unstract developer portal'\n(unchanged)"]
    C --> F["format: password\ntype: string\n(unchanged)"]
    D --> G[User sees 'LLMWhisperer Key'\nlabel in form]
    E --> H[User sees portal\nlink in tooltip/help]

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
unstract/sdk1/src/unstract/sdk1/adapters/x2text/llm_whisperer/src/static/json_schema.json:28
The `title` has been correctly updated to "LLMWhisperer Key", but the `description` still says "Unstract developer portal". For full consistency, the description could also be updated to name the LLMWhisperer portal explicitly — otherwise the label says "LLMWhisperer Key" while the help text directs users to an "Unstract" portal.

```suggestion
      "description": "API key obtained from the [LLMWhisperer developer portal](https://unstract-api-resource.developer.azure-api.net)"
```

### Issue 2 of 2
unstract/sdk1/src/unstract/sdk1/adapters/x2text/llm_whisperer_v2/src/static/json_schema.json:27
Same pattern as in v1: the `title` now reads "LLMWhisperer Key" but the `description` still directs users to the "Unstract developer portal". The two fields are shown together in the adapter config form, so aligning the portal name keeps the messaging consistent.

```suggestion
      "description": "API key obtained from the [LLMWhisperer portal](https://us-central.unstract.com/landing?selectedProduct=llm-whisperer)"
```

_{Reviews (1): Last reviewed commit: "UN-1009 Fix LLMWhisperer adapter key fie..." | Re-trigger Greptile}

Unstract test results

Per-group results

Critical paths

⚠️ Critical paths not yet covered

• auth-login — User can log in and obtain a session cookie. (entry: POST /api/v1/auth/login; declared coverage: no groups declared)
• adapter-register-llm — Register and validate an LLM adapter. (entry: POST /api/v1/adapter/; declared coverage: no groups declared)
• workflow-create-execute — Create a workflow, configure source+destination, execute, poll, fetch result. (entry: POST /api/v1/workflow/{id}/execute/; declared coverage: e2e-workflow)
• api-deployment-run — Deploy a workflow as an API, POST a document, receive structured JSON. (entry: POST /deployment/api/{org}/{name}/; declared coverage: e2e-api-deployment)
• prompt-studio-fetch-response — Prompt Studio: create project, add prompt, run single-pass, get response. (entry: POST /api/v1/prompt-studio/prompt-studio-tool/{id}/fetch_response/; declared coverage: e2e-prompt-studio)
• pipeline-etl-execute — Run an ETL pipeline from source connector to destination. (entry: POST /api/v1/pipeline/{id}/execute/; declared coverage: no groups declared)
• usage-token-tracking — Per-execution token usage is recorded and retrievable. (entry: GET /api/v1/usage/get_token_usage/; declared coverage: no groups declared)
• workflow-execution-fan-out — Multi-file workflow execution fans out to file-processing workers and rejoins. (entry: internal: backend → rabbitmq → workers/file_processing; declared coverage: no groups declared)
• callback-result-delivery — Async results are posted back via the callback worker. (entry: internal: workers/callback → backend /internal endpoints; declared coverage: no groups declared)

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud