Skip to content

Conversation

@yilmaztayfun
Copy link
Contributor

@yilmaztayfun yilmaztayfun commented Dec 16, 2025

Summary by Sourcery

Update schema dependency version and regenerate related task and workflow configuration files.

Build:

  • Bump @burgan-tech/vnext-schema dependency from 0.0.27 to 0.0.28 in package.json and package-lock.json.

Chores:

  • Refresh generated JSON task definitions and HTTP workflow files to align with the updated schema package.

Summary by CodeRabbit

  • Chores
    • Updated API service endpoint configurations across multiple workflows and tasks
    • Bumped schema dependency version

✏️ Tip: You can customize this high-level summary in your review settings.

@sourcery-ai
Copy link

sourcery-ai bot commented Dec 16, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the @burgan-tech/vnext-schema dependency and synchronizes multiple Mockoon task and workflow definitions (JSON and HTTP files) to the new schema, likely adjusting mock server addresses or related endpoint configuration, with lockfile updated accordingly.

File-Level Changes

Change Details Files
Bump vnext schema dependency version and lockfile
  • Update @burgan-tech/vnext-schema devDependency to ^0.0.28
  • Update @burgan-tech/vnext-schema runtime dependency to ^0.0.28
  • Regenerate package-lock.json to reflect the new dependency versions
package.json
package-lock.json
Align Mockoon task JSON definitions with new schema and corrected mock addresses
  • Update account-opening, contract, oauth, payments, and test task JSON definitions to match v0.0.28 schema expectations
  • Adjust any embedded URLs/addresses or structure required by Mockoon to route correctly against the mock server
core/Tasks/account-opening/create-bank-account.json
core/Tasks/account-opening/validate-account-policies.json
core/Tasks/contract/get-contract-documents.json
core/Tasks/contract/render-document.json
core/Tasks/oauth/check-device-registration.json
core/Tasks/oauth/check-push-response.json
core/Tasks/oauth/generate-tokens.json
core/Tasks/oauth/register-device.json
core/Tasks/oauth/send-otp-notification.json
core/Tasks/oauth/send-push-notification.json
core/Tasks/oauth/validate-authorization-code.json
core/Tasks/oauth/validate-client.json
core/Tasks/oauth/validate-user-credentials.json
core/Tasks/oauth/verify-otp-code.json
core/Tasks/payments/activate-payment-schedule.json
core/Tasks/payments/archive-payment-record.json
core/Tasks/payments/deactivate-payment-schedule.json
core/Tasks/payments/get-user-info.json
core/Tasks/payments/increment-retry-counter.json
core/Tasks/payments/process-payment.json
core/Tasks/payments/save-payment-configuration.json
core/Tasks/payments/send-payment-notification-sms.json
core/Tasks/payments/send-payment-push-notification.json
core/Tasks/task-test/test-http-items.json
core/Tasks/task-test/test-http-task.json
Update workflow HTTP definitions to use corrected Mockoon endpoints
  • Update account-opening, contract, oauth, payments, and test workflow HTTP files to hit the corrected Mockoon base URL/ports/paths
  • Ensure request examples align with the updated task JSON mocks and schema
core/Workflows/account-opening/account-opening-workflow.http
core/Workflows/contract/contract-approval-workflow.http
core/Workflows/oauth/oauth-authentication-workflow.http
core/Workflows/payments/scheduled-payments-workflow.http
core/Workflows/task-test/task-test-workflow.http

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@yilmaztayfun yilmaztayfun merged commit fab026f into master Dec 16, 2025
1 of 4 checks passed
@coderabbitai
Copy link

coderabbitai bot commented Dec 16, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This PR replaces all localhost:3001 endpoint references with mockoon:3001 across 27 task and workflow configuration files, plus bumps the @burgan-tech/vnext-schema dependency from ^0.0.27 to ^0.0.28. No functional logic or control-flow changes; purely an environment/host configuration migration.

Changes

Cohort / File(s) Summary
Account-Opening Tasks
core/Tasks/account-opening/create-bank-account.json, validate-account-policies.json
Updated API endpoint host from localhost to mockoon
Contract Tasks
core/Tasks/contract/get-contract-documents.json, render-document.json
Updated API endpoint host from localhost to mockoon
OAuth Tasks
core/Tasks/oauth/check-device-registration.json, check-push-response.json, generate-tokens.json, register-device.json, send-otp-notification.json, send-push-notification.json, validate-authorization-code.json, validate-client.json, validate-user-credentials.json, verify-otp-code.json
Updated API endpoint host from localhost to mockoon across all OAuth task configs
Payments Tasks
core/Tasks/payments/activate-payment-schedule.json, archive-payment-record.json, deactivate-payment-schedule.json, get-user-info.json, increment-retry-counter.json, process-payment.json, save-payment-configuration.json, send-payment-notification-sms.json, send-payment-push-notification.json
Updated API endpoint host from localhost to mockoon across all payments task configs
Task-Test Tasks
core/Tasks/task-test/test-http-items.json, test-http-task.json
Updated API endpoint host from localhost to mockoon
Workflows
core/Workflows/account-opening/account-opening-workflow.http, contract/contract-approval-workflow.http, oauth/oauth-authentication-workflow.http, payments/scheduled-payments-workflow.http, task-test/task-test-workflow.http
Updated Mockoon prerequisite host from localhost:3001 to mockoon:3001
Dependencies
package.json
Bumped @burgan-tech/vnext-schema from ^0.0.27 to ^0.0.28 in both devDependencies and dependencies

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

  • Homogeneous, repetitive find-and-replace pattern across all files
  • Pure configuration change with no logic or control-flow modifications
  • Minimal risk; straightforward verification of consistent host replacement
  • All changes follow identical pattern: localhost:3001mockoon:3001

Possibly related PRs

  • Release v0.0 #7: Modifies the same task and workflow JSON configuration files, switching endpoint hosts between localhost and mockoon for overlapping file sets.

Poem

🐰 From localhost we hop away,
To mockoon's land, to test and play!
Each endpoint now shall find its way,
Through Docker's mesh—hip-hip-hooray!
The schema bumps, our deps grow wise,
Beneath December's testing skies. ✨

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch f/sprint24

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d51455f and 1976cb2.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (31)
  • core/Tasks/account-opening/create-bank-account.json (1 hunks)
  • core/Tasks/account-opening/validate-account-policies.json (1 hunks)
  • core/Tasks/contract/get-contract-documents.json (1 hunks)
  • core/Tasks/contract/render-document.json (1 hunks)
  • core/Tasks/oauth/check-device-registration.json (1 hunks)
  • core/Tasks/oauth/check-push-response.json (1 hunks)
  • core/Tasks/oauth/generate-tokens.json (1 hunks)
  • core/Tasks/oauth/register-device.json (1 hunks)
  • core/Tasks/oauth/send-otp-notification.json (1 hunks)
  • core/Tasks/oauth/send-push-notification.json (1 hunks)
  • core/Tasks/oauth/validate-authorization-code.json (1 hunks)
  • core/Tasks/oauth/validate-client.json (1 hunks)
  • core/Tasks/oauth/validate-user-credentials.json (1 hunks)
  • core/Tasks/oauth/verify-otp-code.json (1 hunks)
  • core/Tasks/payments/activate-payment-schedule.json (1 hunks)
  • core/Tasks/payments/archive-payment-record.json (1 hunks)
  • core/Tasks/payments/deactivate-payment-schedule.json (1 hunks)
  • core/Tasks/payments/get-user-info.json (1 hunks)
  • core/Tasks/payments/increment-retry-counter.json (1 hunks)
  • core/Tasks/payments/process-payment.json (1 hunks)
  • core/Tasks/payments/save-payment-configuration.json (1 hunks)
  • core/Tasks/payments/send-payment-notification-sms.json (1 hunks)
  • core/Tasks/payments/send-payment-push-notification.json (1 hunks)
  • core/Tasks/task-test/test-http-items.json (1 hunks)
  • core/Tasks/task-test/test-http-task.json (1 hunks)
  • core/Workflows/account-opening/account-opening-workflow.http (1 hunks)
  • core/Workflows/contract/contract-approval-workflow.http (3 hunks)
  • core/Workflows/oauth/oauth-authentication-workflow.http (1 hunks)
  • core/Workflows/payments/scheduled-payments-workflow.http (1 hunks)
  • core/Workflows/task-test/task-test-workflow.http (3 hunks)
  • package.json (1 hunks)

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes - here's some feedback:

  • Consider removing the duplicate @burgan-tech/vnext-schema entry from either dependencies or devDependencies in package.json (or clarifying why it must be in both) to reduce maintenance overhead and potential version drift.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider removing the duplicate `@burgan-tech/vnext-schema` entry from either `dependencies` or `devDependencies` in `package.json` (or clarifying why it must be in both) to reduce maintenance overhead and potential version drift.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@gemini-code-assist
Copy link

Summary of Changes

Hello @yilmaztayfun, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the portability and deployment of the application by standardizing the address used to communicate with the Mockoon API. By replacing localhost with mockoon in various configuration files, the system can leverage service discovery mechanisms common in modern deployment environments. Additionally, a minor version update to a core schema dependency is included.

Highlights

  • Mockoon Endpoint Configuration: The hardcoded 'localhost' address for Mockoon API endpoints has been updated to 'mockoon' across numerous task and workflow configuration files. This change ensures that the application can correctly resolve the Mockoon service in containerized or networked environments where 'mockoon' is the designated service name.
  • Dependency Update: The @burgan-tech/vnext-schema dependency has been updated from version 0.0.27 to 0.0.28 in both package.json and package-lock.json.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the Mockoon service address from localhost to mockoon in numerous task definition and workflow test files, which is a good step for containerized environments. It also bumps the @burgan-tech/vnext-schema dependency. The changes are consistent and look correct.

My review includes a couple of suggestions to improve maintainability by avoiding hardcoded URLs. Since many of the modified files appear to be generated, these suggestions should ideally be applied to the source templates or generation scripts:

  • In the JSON task definitions, I recommend using a placeholder for the Mockoon base URL instead of hardcoding it.
  • In the .http test files, I suggest defining and using a variable for the Mockoon base URL, similar to how @baseUrl is already used.

"type": "6",
"config": {
"url": "http://localhost:3001/api/banking/accounts/create",
"url": "http://mockoon:3001/api/banking/accounts/create",

Choose a reason for hiding this comment

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

medium

The base URL for the mock service (http://mockoon:3001) is hardcoded. Since the PR description mentions these files might be generated, it would be best to address this in the generation script or template. Hardcoding URLs across many files can make future configuration changes difficult.

Consider using a placeholder for the base URL in the source template, for example {{mockoonBaseUrl}}, which can be substituted during the generation process. This would centralize the configuration and improve maintainability. This comment applies to all similar task definition files modified in this pull request.


### Test Get Contract Documents (Mockoon)
GET http://localhost:3001/api/contract/documents?groupCode=KG-2024-001
GET http://mockoon:3001/api/contract/documents?groupCode=KG-2024-001

Choose a reason for hiding this comment

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

medium

The Mockoon base URL is hardcoded here. This file already uses a variable @baseUrl for the main application's URL. For better maintainability and consistency, you should define a variable for the Mockoon URL and use it for all Mockoon requests.

Since the PR description mentions these files might be generated, this change should ideally be made in the generator or template for these .http files. For example, you could add @mockoonUrl = http://mockoon:3001 at the top of the template and then use the {{mockoonUrl}} variable in your requests as suggested.

This comment applies to all .http files modified in this pull request.

GET {{mockoonUrl}}/api/contract/documents?groupCode=KG-2024-001

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.

2 participants