feat:Add full_name field to OrganizationMember and ApiProfile

[HavenDV]

Summary by CodeRabbit

• New Features
  • Added optional full name field to organization members and user profile information, enriching the data available through API responses
  • Users can now retrieve full name information alongside other profile details when accessing organization members or user profiles
  • Full backward compatibility maintained; existing integrations continue to work without modifications

[coderabbitai]

Walkthrough

An optional full_name field is added to the OrganizationMember and ApiProfile schemas in the OpenAPI specification. Example payloads are updated to reflect the new nullable string field across affected response objects.

Changes

Cohort / File(s)	Summary
Schema Enhancement src/libs/Ideogram/openapi.yaml	Added optional nullable full_name string property to OrganizationMember and ApiProfile schemas; updated corresponding example payloads to include the new field

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• feat:Make avatar_url optional in ApiProfile OpenAPI schema #113: Modifies the same ApiProfile schema in the same OpenAPI file to make avatar_url optional—both PRs expand optional fields on the same schema definition.

Poem

A rabbit hops through fields of YAML bright,
Adding full_name to shine just right! 🐰
Profiles and members, now more complete,
These nullable strings make the data sweet!

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The pull request title "feat:@coderabbitai" fails to meaningfully describe the changeset. Rather than summarizing the actual change (adding a full_name field to OrganizationMember and ApiProfile schemas in the OpenAPI specification), the title appears to be a bot command addressed to CodeRabbit. While it uses the conventional "feat:" prefix for features, it provides no actual description of what feature was added. The title is vague and non-descriptive, conveying no meaningful information about the changeset to someone reviewing the repository history.	The title should be updated to clearly and concisely describe the main change. A more appropriate title would be something like "feat: add full_name field to OrganizationMember and ApiProfile schemas" or similar, which accurately reflects the addition of the optional full_name field to both schemas in the OpenAPI specification.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 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 555bc40 and 7b6f911.

⛔ Files ignored due to path filters (1)

• src/libs/Ideogram/Generated/Ideogram.Models.OrganizationMember.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

• src/libs/Ideogram/openapi.yaml (2 hunks)

🔇 Additional comments (2)

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

3295-3299: Verify consistency: AI summary claims ApiProfile changes not reflected in code.

The AI summary states full_name was added to the ApiProfile schema, but no marked changes (~) appear in the ApiProfile definition (lines 3064–3126). The OrganizationMember schema has the field properly added as nullable and optional, and examples are consistently updated. Verify whether:

1. ApiProfile schema should also receive the full_name field, or
2. The summary description was inaccurate.

To verify this discrepancy, please check whether the ApiProfile schema at lines 3064–3126 should also include the optional full_name field.

Also applies to: 3253-3253, 3259-3259, 3304-3304

---

3295-3299: LGTM: Optional field properly defined with correct nullability.

The full_name property is correctly implemented as an optional, nullable string field with clear documentation. It is appropriately omitted from the required list of OrganizationMember, maintaining backward compatibility.

---

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