Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Use enums for execution/review statuses#392

Open
Askir wants to merge 1 commit into
mainkviklet/kviklet:mainfrom
refactor-status-enumskviklet/kviklet:refactor-status-enumsCopy head branch name to clipboard
Open

Use enums for execution/review statuses#392
Askir wants to merge 1 commit into
mainkviklet/kviklet:mainfrom
refactor-status-enumskviklet/kviklet:refactor-status-enumsCopy head branch name to clipboard

Conversation

@Askir

@Askir Askir commented Nov 3, 2025

Copy link
Copy Markdown
Member

Summary

  • change ExecutionRequest DTOs to expose ExecutionStatus/ReviewStatus enums instead of strings
  • update ExecutionRequestAdapter mapping and helper factories accordingly

Testing

  • ./gradlew test --tests dev.kviklet.kviklet.ExecutionRequestTest

Important

Change ExecutionRequest DTOs and related classes to use enums for ExecutionStatus and ReviewStatus instead of strings.

  • Behavior:
    • Change ExecutionRequest DTOs to use ExecutionStatus and ReviewStatus enums instead of strings.
    • Update ExecutionRequestAdapter to map and handle these enums.
  • DTOs:
    • Modify ExecutionRequest in ExecutionRequest.kt to use enums for executionStatus and reviewStatus.
    • Update DatasourceExecutionRequest and KubernetesExecutionRequest to use enums.
  • Entities:
    • Update ExecutionRequestEntity in ExecutionRequest.kt to use enums for executionStatus and reviewStatus.
  • Factories:
    • Update ExecutionRequestFactory in ExecutionRequestFactory.kt to use enums for executionStatus and reviewStatus.

This description was created by Ellipsis for 3a74dfa. You can customize this summary. It will automatically update as commits are pushed.

@ellipsis-dev ellipsis-dev Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Important

Looks good to me! 👍

Reviewed everything up to 3a74dfa in 1 minute and 14 seconds. Click for details.
  • Reviewed 109 lines of code in 3 files
  • Skipped 0 files when reviewing.
  • Skipped posting 3 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. backend/src/main/kotlin/dev/kviklet/kviklet/db/ExecutionRequest.kt:100
  • Draft comment:
    Mapping changes: now passing the enum objects directly (executionStatus and reviewStatus) instead of using .name. Ensure that JSON serialization/deserialization for these enums remains consistent with API expectations.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the author to ensure that JSON serialization/deserialization remains consistent, which is a form of asking the author to double-check their work. This violates the rule against asking the author to ensure behavior is intended or tested.
2. backend/src/main/kotlin/dev/kviklet/kviklet/service/dto/ExecutionRequest.kt:52
  • Draft comment:
    DTO update: executionStatus and reviewStatus are now defined as enums instead of strings. This enhances type safety, but ensure consumers of the API are updated if they relied on string values.
  • Reason this comment was not posted:
    Comment looked like it was already resolved.
3. backend/src/test/kotlin/dev/kviklet/kviklet/helper/ExecutionRequestFactory.kt:157
  • Draft comment:
    Test factory updated: default values for executionStatus (now EXECUTABLE) and reviewStatus (AWAITING_APPROVAL) have been changed. Verify that these defaults align with the intended business logic.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to verify if the changes align with the intended business logic, which is against the rules. It does not provide a specific suggestion or ask for a specific test to be written. Therefore, it should be removed.

Workflow ID: wflow_K6JjmQQCE38zhub4

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.