feat:Add boolean private (default false) to ModelMeta in OpenAPI

[HavenDV]

Summary by CodeRabbit

• New Features

  • Added a “private” boolean attribute to model metadata in the public API. Defaults to false and appears in API requests/responses for model details.
  • Backward compatible: no existing fields or requirements changed.

• Documentation

  • OpenAPI schema updated to include the new “private” field in ModelMeta, clarifying its type, default, and placement.

[coderabbitai]

Walkthrough

Adds a new boolean field private (default: false) to the ModelMeta schema in the OpenAPI specification at src/libs/DeepInfra/openapi.yaml.

Changes

Cohort / File(s)	Summary
OpenAPI spec update src/libs/DeepInfra/openapi.yaml	Added ModelMeta.properties.private (title: Private, type: boolean, default: false) after plan_id; no other ModelMeta changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my ears at schemas neat,
A toggle added—private, discreet.
In YAML fields where models dwell,
A boolean whisper: shh, don’t tell.
I thump my paws, commit complete—
Carrot-shaped flags make specs more sweet! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The provided title "feat:@coderabbitai" is an automated/mention-style label and does not describe the actual change in this PR (adding a boolean private property to ModelMeta in src/libs/DeepInfra/openapi.yaml), so it is too vague for a reviewer scanning history. Because it neither summarizes the main change nor provides scope, the title is inconclusive relative to the changeset. Reviewers cannot rely on it to understand the primary purpose of the PR at a glance.	Please rename the PR to a concise, descriptive title such as "feat(openapi): add private boolean to ModelMeta" or "Add ModelMeta.private to OpenAPI schema" and remove the @mention; optionally add a short description referencing src/libs/DeepInfra/openapi.yaml and why the field was added so reviewers immediately understand the change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ 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_202509181519

---

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

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

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

6859-6862: Type mismatch: ModelOut.private is integer; ModelMeta.private is boolean. Align to boolean.

This will otherwise generate inconsistent SDK types and surprise clients.

-        private:
-          title: Private
-          type: integer
-          default: 0
+        private:
+          title: Private
+          type: boolean
+          default: false

🧹 Nitpick comments (2)

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

4616-4620: Document the new field’s behavior.

Add a short description clarifying visibility semantics (who can see/use a private model; listing/search effects).

         private:
           title: Private
           type: boolean
           default: false
+          description: Whether the model is private (not publicly listed; visible/usable only to the owner/team).

---

4616-4620: Avoid dual “public” and “private” flags across schemas.

ModelInfoOut exposes public: boolean while ModelMeta/ModelOut expose private. Prefer a single polarity everywhere (e.g., public) or clearly mark one as deprecated and document mapping.

Also applies to: 6613-6615

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 40df308 and d782284.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

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

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Test / Build, test and publish