WRITER integration support

[adeweaver]

Important

Add WRITER to supported LLM Foundation Models in supported.mdx.

• Documentation:
  • Add WRITER to the list of supported LLM Foundation Models in supported.mdx with both Python and Typescript support.

^{This description was created by for 9ce5870. You can customize this summary. It will automatically update as commits are pushed.}

Summary by CodeRabbit

• Documentation
  • Added WRITER to the LLM Foundation Models table, including a link to writer.com.
  • Indicated full support with Python and TypeScript (✅).
  • Positioned the entry after HuggingFace Transformers for easier discovery.
  • No functional or behavioral changes; documentation update only.

[coderabbitai]

Walkthrough

Added a new WRITER row to the LLM Foundation Models table in openllmetry/tracing/supported.mdx, indicating Python and TypeScript support, placed after HuggingFace Transformers. No other files or behaviors changed.

Changes

Cohort / File(s)	Summary
Docs: Supported Models Table openllmetry/tracing/supported.mdx	Inserted WRITER entry in the LLM Foundation Models table with ✅ for Python and TypeScript; positioned after HuggingFace Transformers. No other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (3 passed)

✅ 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 "WRITER integration support" is concise and directly reflects the primary change in the PR—adding WRITER to the LLM Foundation Models table in supported.mdx—so it clearly communicates the main intent to reviewers and history readers.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A hop and a skip through markdown meadows bright,
I nibbled a row and set WRITER just right.
Checkmarks twinkle—Py and TS in line,
No code disturbed, the docs look fine.
Thump-thump! says the reviewer’s light delight.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 9ce5870 in 26 seconds. Click for details.

• Reviewed 12 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. openllmetry/tracing/supported.mdx:29

• Draft comment:
  Added WRITER integration documentation. Verify that its placement in the LLM table follows the intended order and that support in both Python and Typescript is accurate.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_5BOkzPxUAySfowWz

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

openllmetry/tracing/supported.mdx (1)

29-29: Use brand-correct casing: “Writer” (not all caps).

Matches brand style used elsewhere in the table (e.g., “OpenAI”, “Groq”) and improves consistency.

-| [WRITER](https://writer.com/)                                                         | ✅     | ✅         |
+| [Writer](https://writer.com/)                                                         | ✅     | ✅         |

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2bb435c and 9ce5870.

📒 Files selected for processing (1)

• openllmetry/tracing/supported.mdx (1 hunks)

🔇 Additional comments (1)

openllmetry/tracing/supported.mdx (1)

29-29: Replace WRITER homepage with their SDK docs & confirm Python/TS support

No local Writer integration page found — update openllmetry/tracing/supported.mdx to link to Writer’s SDK documentation and ensure both the Python and TypeScript (Node) columns are correct; Writer publishes official Python and Node/TypeScript SDKs. (dev.writer.com)