Skip to content

Conversation

@tisnik
Copy link
Contributor

@tisnik tisnik commented Aug 5, 2025

Description

LCORE-336: Regenerate OpenAPI 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-336

Summary by CodeRabbit

  • Documentation
    • Updated the API documentation for conversation details to replace the "session_data" object with a new "chat_history" array, providing a clearer representation of conversation history with message groups and timing information.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 5, 2025

Walkthrough

The OpenAPI specification for the GET /v1/conversations/{conversation_id} endpoint has been updated. The response schema now provides a chat_history array, replacing the previous session_data object. Each chat_history entry contains grouped messages with content, type, and timing metadata.

Changes

Cohort / File(s) Change Summary
OpenAPI Spec Update
docs/openapi.json
Modified the response schema for GET /v1/conversations/{conversation_id}: replaced session_data with a chat_history array, detailing conversation history as message groups with timestamps.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant API Server

    Client->>API Server: GET /v1/conversations/{conversation_id}
    API Server-->>Client: Responds with { chat_history: [ { messages: [...], started_at, completed_at }, ... ] }
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • LCORE-304: Update OpenAPI schema #258: Adds the /v1/conversations/{conversation_id} endpoint and related schemas, which is closely related to this schema update but does not modify the same definitions.

Poem

In the warren of code, a history anew,
Session data hops away, chat histories in view.
Each message a carrot, each timestamp a clue—
Conversations now grouped, with context to chew!
🐇✨

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
🪧 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.
  • 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.

Support

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

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1faea65 and 5ad1ce3.

📒 Files selected for processing (1)
  • docs/openapi.json (1 hunks)
🔇 Additional comments (1)
docs/openapi.json (1)

400-415: Validate regenerated OpenAPI spec in CI

To avoid blocking CI later, install the validator locally and ensure its CLI is on $PATH before running:

#!/bin/bash
# Install the OpenAPI spec validator into ~/.local/bin and add it to PATH
pip install --user --quiet openapi-spec-validator==0.7.1
export PATH="$HOME/.local/bin:$PATH"

# Validate the spec against OpenAPI 3.1 meta-schema
openapi-spec-validator docs/openapi.json

This command will exit with a non-zero status if the spec (e.g. misplaced example keys) is invalid.

Comment on lines +400 to +415
"chat_history": [
{
"messages": [
{
"content": "Hi",
"type": "user"
},
{
"content": "Hello!",
"type": "assistant"
}
],
"started_at": "2024-01-01T00:00:00Z",
"completed_at": "2024-01-01T00:00:05Z"
}
]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Misplaced example fields – current structure is not OpenAPI-compliant

conversation_id and chat_history are placed as siblings of content, but OpenAPI 3.x only allows the keys description, headers, content, and links inside a Response Object.
These two keys are therefore silently ignored by tooling (e.g., generators, validators) and break example rendering.

Refactor by moving the example under the proper media-type object:

-                        "conversation_id": "123e4567-e89b-12d3-a456-426614174000",
-                        "chat_history": [
-                            {
-                                "messages": [
-                                    {"content": "Hi",       "type": "user"},
-                                    {"content": "Hello!",   "type": "assistant"}
-                                ],
-                                "started_at":  "2024-01-01T00:00:00Z",
-                                "completed_at":"2024-01-01T00:00:05Z"
-                            }
-                        ]
+                        "content": {
+                            "application/json": {
+                                "schema": {
+                                    "$ref": "#/components/schemas/ConversationResponse"
+                                },
+                                "example": {
+                                    "conversation_id": "123e4567-e89b-12d3-a456-426614174000",
+                                    "chat_history": [
+                                        {
+                                            "messages": [
+                                                {"content": "Hi",     "type": "user"},
+                                                {"content": "Hello!", "type": "assistant"}
+                                            ],
+                                            "started_at":  "2024-01-01T00:00:00Z",
+                                            "completed_at":"2024-01-01T00:00:05Z"
+                                        }
+                                    ]
+                                }
+                            }
+                        }

Without this change, openapi-generator, swagger-ui, and code-gen clients will not surface the example or may even reject the spec.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In docs/openapi.json around lines 400 to 415, the fields `conversation_id` and
`chat_history` are incorrectly placed as siblings to `content` inside a Response
Object, which violates OpenAPI 3.x specifications. To fix this, move these
example fields inside the `example` or `examples` property under the appropriate
media-type object within `content`. This ensures the example is correctly
recognized by OpenAPI tools and generators.

@tisnik tisnik merged commit 12dcea3 into lightspeed-core:main Aug 5, 2025
17 of 18 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Oct 6, 2025
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant