Skip to content

LCORE-247: Getting started guide: Usage section#333

Merged
tisnik merged 3 commits intolightspeed-core:mainfrom
tisnik:lcore-247-getting-started-usage
Aug 3, 2025
Merged

LCORE-247: Getting started guide: Usage section#333
tisnik merged 3 commits intolightspeed-core:mainfrom
tisnik:lcore-247-getting-started-usage

Conversation

@tisnik
Copy link
Contributor

@tisnik tisnik commented Aug 3, 2025

Description

LCORE-247: Getting started guide: Usage section

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
    • Added a comprehensive "Usage" section to the getting started guide, including step-by-step instructions for interacting with the service via Swagger UI and command-line curl commands.
    • Included example API requests, responses, and screenshots to help users explore and use the available REST API endpoints.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 3, 2025

Walkthrough

A new "Usage" section was added to the docs/getting_started.md file. This section provides detailed instructions and examples for interacting with the Lightspeed Core Stack service using both the Swagger UI and command-line curl commands. No existing documentation or code was modified.

Changes

Cohort / File(s) Change Summary
Documentation - Usage Instructions
docs/getting_started.md
Added a comprehensive "Usage" section detailing how to interact with the Lightspeed Core Stack service via Swagger UI and curl, including example requests, responses, and screenshot references.

Sequence Diagram(s)

Not applicable: Only documentation content was added.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

A nibble of docs, a hop through the stack,
Now bunnies can query and never look back!
Swagger or curl, the choices abound—
With markdown and JSON, the answers are found.
So thump your soft paws, let’s give a cheer,
For clearer instructions, the path is now clear! 🐇✨

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

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: 0

🧹 Nitpick comments (4)
docs/getting_started.md (4)

47-55: Fix list indentation to satisfy MD007 and improve readability

The nested list under “Usage” is indented with 4 spaces instead of the expected 2-space / 2-level pattern. This breaks consistent rendering in some Markdown renderers and is flagged by markdownlint.

-* [Usage](#usage)
-    * [Using OpenAPI Swagger UI](#using-openapi-swagger-ui)
-        * [Front page](#front-page)
-        * [Swagger UI](#swagger-ui)
-        * [Sending query to LLM](#sending-query-to-llm)
-    * [Using `curl`](#using-curl)
-        * [Accessing `info` REST API endpoint](#accessing-info-rest-api-endpoint)
-        * [Retrieving list of available models](#retrieving-list-of-available-models)
-        * [Retrieving LLM response](#retrieving-llm-response)
+* [Usage](#usage)
+  * [Using OpenAPI Swagger UI](#using-openapi-swagger-ui)
+    * [Front page](#front-page)
+    * [Swagger UI](#swagger-ui)
+    * [Sending query to LLM](#sending-query-to-llm)
+  * [Using `curl`](#using-curl)
+    * [Accessing `info` REST API endpoint](#accessing-info-rest-api-endpoint)
+    * [Retrieving list of available models](#retrieving-list-of-available-models)
+    * [Retrieving LLM response](#retrieving-llm-response)

1697-1699: Convert bare URL to Markdown link

Bare URLs trigger MD034 and can break line wrapping. Prefer angle brackets or link syntax.

-Open http://localhost:8080 URL in your web browser. The following front page should be displayed:
+Open <http://localhost:8080> in your web browser. The following front page should be displayed:

1707-1708: Correct product name typo

“Ligthspeed” → “Lightspeed”.

-... actual response from the Ligthspeed Core Stack service:
+... actual response from the Lightspeed Core Stack service:

1855-1857: Fix spelling

“containt” → “contain”.

-> As is shown on the previous example, the output might containt endlines, Markdown marks etc.
+> As shown in the previous example, the output might contain new lines, Markdown markup, etc.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1c95a1a and 83c6eac.

⛔ Files ignored due to path filters (5)
  • docs/screenshots/front_page.jpg is excluded by !**/*.jpg
  • docs/screenshots/info_endpoint.png is excluded by !**/*.png
  • docs/screenshots/openapi_swagger.png is excluded by !**/*.png
  • docs/screenshots/query_request.png is excluded by !**/*.png
  • docs/screenshots/query_response.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • docs/getting_started.md (2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/getting_started.md

48-48: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


49-49: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


50-50: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


51-51: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


52-52: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


53-53: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


54-54: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


55-55: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


1697-1697: Bare URL used

(MD034, no-bare-urls)

🪛 LanguageTool
docs/getting_started.md

[grammar] ~1707-~1707: Ensure spelling is correct
Context: .../info) and see actual response from the Ligthspeed Core Stack service: ![Swagger UI page]...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~1856-~1856: Ensure spelling is correct
Context: ... the previous example, the output might containt endlines, Markdown marks etc.

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (1)
docs/getting_started.md (1)

1703-1710: Duplicate screenshot reference

Both the “Swagger UI” subsection and the “Sending query to LLM” subsection embed openapi_swagger.png. If this is intentional, ignore; otherwise consider using distinct screenshots or omitting one to reduce noise.

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: 0

🧹 Nitpick comments (4)
docs/getting_started.md (4)

47-55: Fix list-indentation to satisfy markdownlint (MD007)
The new “Usage” TOC block uses 4/8-space indentation, while the rest of the document and MD007 expect 2/4. Aligning indentation avoids future linter noise.

-* [Usage](#usage)
-    * [Using OpenAPI Swagger UI](#using-openapi-swagger-ui)
-        * [Front page](#front-page)
-        * [Swagger UI](#swagger-ui)
-        * [Sending query to LLM](#sending-query-to-llm)
-    * [Using `curl`](#using-curl)
-        * [Accessing `info` REST API endpoint](#accessing-info-rest-api-endpoint)
-        * [Retrieving list of available models](#retrieving-list-of-available-models)
-        * [Retrieving LLM response](#retrieving-llm-response)
+* [Usage](#usage)
+  * [Using OpenAPI Swagger UI](#using-openapi-swagger-ui)
+    * [Front page](#front-page)
+    * [Swagger UI](#swagger-ui)
+    * [Sending query to LLM](#sending-query-to-llm)
+  * [Using `curl`](#using-curl)
+    * [Accessing `info` REST API endpoint](#accessing-info-rest-api-endpoint)
+    * [Retrieving list of available models](#retrieving-list-of-available-models)
+    * [Retrieving LLM response](#retrieving-llm-response)

1696-1721: Clarify screenshots & alt-text
The same image name (openapi_swagger.png) is reused three times (Lines 1705, 1716, 1720) with identical alt-text “Swagger UI page”, making it unclear which step each screenshot represents. Either capture distinct screenshots or reuse a single reference once and adjust surrounding wording.
Also consider a more descriptive alt-text (e.g. “/query request body example”) to improve accessibility.


1713-1716: Minor grammar – “sent”, not “send”

-Some REST API endpoints like `/query` requires payload to be send into the service.
+Some REST API endpoints, like `/query`, require a JSON payload to be sent to the service.

1833-1836: Minor grammar – “sent” & flow

-To retrieve LLM response, the question (or query) needs to be send to inference model. Thus the `HTTP POST` method should be used:
+To retrieve an LLM response, the question (or query) must be sent to the inference model; therefore, the `HTTP POST` method should be used:
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 83c6eac and feff3bd.

📒 Files selected for processing (1)
  • docs/getting_started.md (2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/getting_started.md

48-48: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


49-49: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


50-50: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


51-51: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


52-52: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


53-53: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


54-54: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


55-55: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)

@tisnik tisnik merged commit 8616b2e into lightspeed-core:main Aug 3, 2025
17 of 18 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Aug 4, 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