Skip to content

feat: add GET /api/v1/check endpoint#244

Merged
UlisesGascon merged 2 commits intomainfrom
ulises/v1-check-list
Jun 16, 2025
Merged

feat: add GET /api/v1/check endpoint#244
UlisesGascon merged 2 commits intomainfrom
ulises/v1-check-list

Conversation

@UlisesGascon
Copy link
Member

@UlisesGascon UlisesGascon commented Jun 16, 2025

Related #216

image

Summary by CodeRabbit

  • New Features

    • Introduced a new API endpoint /api/v1/check to retrieve a list of all checks.
    • Added comprehensive API documentation for the new endpoint, including a detailed schema for returned check objects.
  • Tests

    • Added tests to verify the new endpoint returns the correct data and handles server errors appropriately.

@UlisesGascon UlisesGascon self-assigned this Jun 16, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jun 16, 2025

Walkthrough

A new API endpoint, GET /api/v1/check, was introduced to return a list of all compliance checks. Supporting changes include the addition of a store method to retrieve all checks, test coverage for the new endpoint, and the corresponding OpenAPI documentation with a detailed schema for the check objects.

Changes

File(s) Change Summary
src/store/index.js Added getAllChecks method to retrieve all records from compliance_checks.
src/httpServer/routers/apiV1.js Added GET /api/v1/check route handler using getAllChecks.
src/httpServer/swagger/api-v1.yml Documented new endpoint and introduced the Check schema with detailed properties and requirements.
tests/httpServer/apiV1.test.js Added tests for GET /api/v1/check, including success and error scenarios.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant API_Router
    participant Store

    Client->>API_Router: GET /api/v1/check
    API_Router->>Store: getAllChecks()
    Store-->>API_Router: [Array of Check objects]
    API_Router-->>Client: 200 OK + JSON array of checks
    alt Error occurs
        API_Router-->>Client: 500 Internal Server Error + error message
    end
Loading

Poem

A hop and a skip, a new route to check,
Now listing compliance, what the server expects!
With schemas and tests, the code's looking neat,
All checks in a row, a developer's treat.
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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

@UlisesGascon UlisesGascon force-pushed the ulises/v1-check-list branch from 1eabdd0 to 7bb1e80 Compare June 16, 2025 13:28
@UlisesGascon UlisesGascon added this to the v1.0.0 milestone Jun 16, 2025
Copy link

@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

🔭 Outside diff range comments (1)
src/store/index.js (1)

219-253: Duplicate accessor clutters the public API

getAllComplianceChecks (line 220) and the newly-added getAllChecks (line 252) expose the same data. Two names for the same thing will confuse consumers and make refactors harder.

-    getAllComplianceChecks: () => getAll('compliance_checks'),
+    // Deprecated alias – remove once all callers migrate to getAllChecks
+    // getAllComplianceChecks: () => getAll('compliance_checks'),
     …
     getAllChecks: () => getAll('compliance_checks')

Either keep a single canonical accessor or add a deprecation note/alias for backward compatibility.

🧹 Nitpick comments (4)
src/httpServer/routers/apiV1.js (1)

124-132: Endpoint lacks pagination & could DoS the service

/check returns the full compliance_checks table in one go. On large deployments this may lead to huge payloads and long DB scans.

Quick win:

-const checks = await getAllChecks()
-res.json(checks)
+const { limit = 100, offset = 0 } = req.query
+const checks = await knex('compliance_checks')
+  .limit(limit)
+  .offset(offset)
+  .select('*')
+res.json(checks)

At minimum add limit / offset query-string handling and reflect it in the OpenAPI spec.

__tests__/httpServer/apiV1.test.js (1)

393-404: Test compares serialised blobs – use explicit shape assertions

Stringifying both sides hides subtle divergences (e.g., type coercion, missing fields). Prefer matching selected fields or deep equality with proper Date handling:

-// @TODO: find a more elegant way to solve the issue with the date format
-expect(response.body).toStrictEqual(JSON.parse(JSON.stringify(storedChecks)))
+expect(response.body).toHaveLength(storedChecks.length)
+storedChecks.forEach((check, idx) => {
+  expect(response.body[idx]).toMatchObject({
+    id: check.id,
+    code_name: check.code_name,
+    title: check.title
+  })
+})

Makes failures more readable and resilient to cosmetic differences.

src/httpServer/swagger/api-v1.yml (2)

214-235: Trailing whitespace breaks yamllint & CI

Line 362 (and a few others) contains a stray space, flagged by YAMLlint. Remove it to keep the spec lint-clean.

+362

214-235: Plural noun recommended for collection endpoint

REST conventions favour plural resources (/checks) when returning a collection. Consider renaming the path and operation to keep the API consistent (/projects, /workflows, etc.).

Update router, tests, and spec accordingly if you decide to adopt this.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5e7e681 and 7bb1e80.

📒 Files selected for processing (4)
  • __tests__/httpServer/apiV1.test.js (3 hunks)
  • src/httpServer/routers/apiV1.js (2 hunks)
  • src/httpServer/swagger/api-v1.yml (2 hunks)
  • src/store/index.js (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
src/httpServer/swagger/api-v1.yml

[error] 362-362: trailing spaces

(trailing-spaces)

🔇 Additional comments (1)
src/httpServer/routers/apiV1.js (1)

30-30: Destructuring now depends on the duplicate store method

getAllChecks is imported, but getAllComplianceChecks is still exported by the store. If the duplication is resolved (see store comment) make sure this destructuring is updated accordingly; otherwise the router will break at runtime.

@UlisesGascon UlisesGascon merged commit 981ce19 into main Jun 16, 2025
7 checks passed
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