feat:Add optional meta_title and meta_description to ModelFamilyOut

[HavenDV]

Summary by CodeRabbit

• New Features

  • Added optional SEO metadata fields to model family entities in the public API: meta_title and meta_description. These enable richer titles and descriptions in integrations and listings.

• Documentation

  • Updated API schema documentation to include the new SEO fields and usage details.

[coderabbitai]

Walkthrough

The OpenAPI schema in src/libs/DeepInfra/openapi.yaml was updated to add two optional, nullable string fields—meta_title and meta_description—to ModelFamilyOut for SEO-related metadata. No existing fields or required constraints were changed.

Changes

Cohort / File(s)	Summary of changes
OpenAPI Schema Update src/libs/DeepInfra/openapi.yaml	Added optional nullable strings to ModelFamilyOut: meta_title (Meta Title, SEO) and meta_description (Meta Description, SEO). No removals or required fields changed.

Sequence Diagram(s)

sequenceDiagram
    participant C as API Client
    participant S as DeepInfra API

    C->>S: GET /model-families/{id}
    activate S
    S-->>C: 200 OK<br/>ModelFamilyOut { ... , meta_title?, meta_description? }
    deactivate S

    Note over C,S: meta_title and meta_description are optional and nullable

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers at metadata’s light,
Two new fields hop in—SEO in sight.
meta_title gleams, description takes flight,
Optional carrots, nullable and bright.
In YAML meadows, schemas feel right. 🥕🐇

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bot/update-openapi_202509021520

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/libs/DeepInfra/openapi.yaml (1)

6487-6496: Harden SEO fields: make output-only, cap lengths, and guard against newlines

If these are rendered into HTML meta tags, add readOnly, reasonable maxLength, and a newline guard to avoid broken tags and bloated SERP snippets. If you plan to allow writes later, introduce a separate ModelFamilyMetaIn for inputs instead of loosening the Out schema.

Please confirm whether these are strictly server-derived (preferred). If yes, adopt the patch below.

       meta_title:
         title: Meta Title
         type: string
         description: Meta title for SEO
         nullable: true
+        readOnly: true
+        maxLength: 70
+        pattern: '^[^\r\n]*$'
+        example: "Llama 3 — Model family overview"
       meta_description:
         title: Meta Description
         type: string
         description: Meta description for SEO
         nullable: true
+        readOnly: true
+        maxLength: 160
+        pattern: '^[^\r\n]*$'
+        example: "Specs, pricing, and usage guidance for the Llama 3 model family."

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• 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 2da937b and 00e46a8.

⛔ Files ignored due to path filters (1)

• src/libs/DeepInfra/Generated/DeepInfra.Models.ModelFamilyOut.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

• src/libs/DeepInfra/openapi.yaml (1 hunks)