LCORE-247: regenerated schema

[tisnik]

Description

LCORE-247: regenerated schema

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Related Tickets & Documents

• Related Issue #LCORE-247

Summary by CodeRabbit

• Documentation
  • Updated API documentation to reflect that feedback is enabled by default and transcripts are disabled by default in user data collection settings. Titles and default values for these settings have been revised for clarity.

[coderabbitai]

Walkthrough

The OpenAPI specification was updated to modify the default values and titles for the feedback_enabled and transcripts_enabled properties in the user data collection settings. The example configuration and schema definitions were adjusted to reflect that feedback is enabled and transcripts are disabled by default.

Changes

File(s)	Change Summary
docs/openapi.json	Updated feedback_enabled and transcripts_enabled property titles and default values in schema and example configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a skip, a tweak in the spec,
Feedback now on, transcripts in check.
Titles aligned, defaults anew,
The docs are refreshed—so clear and true!
With every small change, the system feels bright,
A rabbit’s delight in the OpenAPI light.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ 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

🪧 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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

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

Documentation and Community

• 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)

docs/openapi.json (1)

1564-1566: transcripts_enabled title updated but default flipped – ensure spec wording matches

The field is now titled “Transcripts Enabled” but defaults to false (disabled).
Confirm that accompanying documentation and UI labels reflect disabled by default rather than “enabled”.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7215f44 and 33a7e8c.

📒 Files selected for processing (1)

• docs/openapi.json (3 hunks)

🔇 Additional comments (2)

docs/openapi.json (2)

254-257: Example payload now diverges from the declared defaults – double-check intent

feedback_enabled is true here while the schema default (see lines 1548-1550) is false.
If the service truly wants feedback enabled by default, either:

1. keep the example as-is and flip the schema default back to true, or
2. leave the schema as-is (false) and set the example to false to avoid confusion.

Please confirm which behaviour is correct and align example + default (and any release notes) accordingly.

---

1548-1550: Confirm breaking change: feedback_enabled default flipped to false
File: docs/openapi.json (lines 1548–1550)

    "title": "Feedback Enabled",
    "default": false

For clients omitting this field, feedback will now be disabled. Please verify that:

• Downstream components tolerate the new default
• The changelog or API version clearly documents this behavioral change
• If unintended, revert to "default": true or bump the API version