feat:Add recraftv4 enum to TransformModel in src/libs/Recraft/openapi.yaml

[HavenDV]

Summary by CodeRabbit

• New Features

  • Added support for the new “recraftv4” transform model in the API schema, allowing clients to select this model in transform requests.
  • No breaking changes; existing models remain available.

• Chores

  • Updated the public schema so tools and SDK generators can recognize the new model after refreshing or regenerating clients. Users who validate requests against the schema may need to update to access “recraftv4.”

[coderabbitai]

Walkthrough

Added a new enum value recraftv4 to TransformModel in src/libs/Recraft/openapi.yaml. No other changes.

Changes

Cohort / File(s)	Summary
OpenAPI schema update src/libs/Recraft/openapi.yaml	Added recraftv4 to the TransformModel enum list.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat:Add qwen_image and gemini_25_flash_image to TransformModel enum #64 — Also updates the TransformModel enum in src/libs/Recraft/openapi.yaml by adding qwen_image and gemini_25_flash_image, touching the same schema area.

Poem

A nibble of schema, a hop in the night,
I add recraftv4—just the enum’s delight.
No fields rearranged, no swaggering fuss,
One shiny new value, approved by us.
Thump-thump! says the rabbit, “Merge it just right.”

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title "feat:@coderabbitai" does not describe the change in this PR, which adds the enum value "recraftv4" to the TransformModel enum in src/libs/Recraft/openapi.yaml; it reads like a bot/author tag rather than a concise summary of the primary change, so it is too vague to judge relevance. Under the check rules a vague or generic title is inconclusive because it fails to communicate the main change to reviewers. This title therefore does not provide enough information to be considered a clear, descriptive PR title.	Please update the PR title to a short, specific summary of the primary change, for example: "feat(openapi): add recraftv4 to TransformModel enum" or "chore(openapi): add recraftv4 enum value"; avoid bot mentions and keep the scope and intent clear so reviewers can understand the main change at a glance.

✅ 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_202509222108

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c518e5c and a25454d.

⛔ Files ignored due to path filters (1)

• src/libs/Recraft/Generated/Recraft.Models.TransformModel.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

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

865-888: Confirm backend accepts recraftv4; C# client regenerated — update docs/examples

Observed: src/libs/Recraft/openapi.yaml includes recraftv4 in TransformModel; generated C# includes Recraftv4 and converters (src/libs/Recraft/Generated/Recraft.Models.TransformModel.g.cs and related JsonConverters).

Actions:

• Verify runtime/backend actually accepts/serves recraftv4 (integration/API test or server validation).
• Update any docs/examples that list allowed models.
• Regenerate other SDKs if applicable (C# appears regenerated).

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.

---

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