You are working on the hyperswitch repository (Rust payment processing system).…
- User
You are working on the hyperswitch repository (Rust payment processing system).
REPOSITORY SETUP:
- Repository: juspay/hyperswitch
- Working directory: ./repos/hyperswitch_pool_3 (already cloned)
- Base commit: 9d7edb5cee030a13c8699a914a0d3600b058853d
- Task ID: juspay__hyperswitch-8491
- Version: v1.115.0
TASK DESCRIPTION: Bug: [FEATURE] celero connector template
Feature Description
Create connector template
Possible Implementation
https://celerocommerce.com/developers/
Have you spent some time checking if this feature request has been raised before?
- I checked and didn't find a similar issue
Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit a PR?
None
DETAILED CONTEXT & HINTS:
Type of Change
- Bugfix
- New feature
- Enhancement
- Refactoring
- Dependency updates
- Documentation
- CI/CD
Description
Template new connection integration
celeroAdditional Changes
- This PR modifies the API contract
- This PR modifies the database schema
- This PR modifies application configuration/environment variables
Motivation and Context
How did you test it?
No testing required as this is template
Checklist
- I formatted the code
cargo +nightly fmt --all - I addressed lints thrown by
cargo clippy - I reviewed the submitted code
- I added unit tests for my changes where possible
CRITICAL INSTRUCTIONS - WORK FAST AND EFFICIENTLY:
-
Create DENSE, ACTION-FOCUSED todos IMMEDIATELY
- Make todos specific and actionable
- Focus on HIGH-IMPACT actions only
- 5-8 todos maximum - be surgical, not exhaustive
-
Execute aggressively:
- Use bash commands to search efficiently
- Read multiple related files in quick succession
- Make ALL related changes in one edit
- Skip unnecessary exploration
-
File operations:
- All repo files: './repos/hyperswitch_pool_3/'
- Use targeted edits over whole file rewrites
-
NO TESTING UNLESS CRITICAL:
- Focus on making the actual code changes
- Only test if explicitly required
-
Maximize information density:
- Each turn should accomplish significant work
- Batch file reads when examining related code
- Use search commands to locate code quickly
EFFICIENCY IS CRITICAL. Make substantial progress every turn.
Assistant
I'll help you implement the Celero connector template for the Hyperswitch repository. Let me start by exploring the codebase to understand how connectors are structured and then create the template.
First, let me look at the current connector structure to understand how to implement the Celero template.
Assistant
Let me first check the current git status to understand what files we're working with:
Assistant
Now let me look at the crates directory to understand the connector structure:
Assistant
Let me check the connector directory structure:
Assistant
(no content)
Assistant
Let me look at the connectors directory to understand the structure better:
Assistant
Let me also check the connector-template directory to understand how templates are created:
Assistant
Now let me check how existing connectors are implemented by looking at a few examples:
Assistant
Let me read a simpler connector file to understand the pattern:
Assistant
Let me also look at the transformers module for the dummy connector:
Assistant
Now I need to understand what Celero is and create a template. Let me first research Celero:
Assistant
Let me also look at the connectors.rs file to understand how connectors are registered:
Assistant
Let me also check the connector template files to understand the pattern:
Assistant
Let me also look at the transformers file for the template:
Assistant
Now I have enough information to create a Celero connector template. Let me create the todos:
Assistant
I'll create the Celero connector template for Hyperswitch. Let me first create the directory structure and files for the Celero connector.
Assistant
Let me check what directories exist first:
Assistant
Now let me create the Celero connector module. I'll first create the connector.rs file:
Assistant
I'll continue working on implementing the Celero connector template. Let me start by creating the directory structure and the main connector file:
Assistant
I'll implement the Celero connector template for Hyperswitch by creating the necessary files directly. Let me first examine what I have to work with, then implement the Celero connector.
Assistant
I'll implement the Celero connector by creating the necessary files directly. Let me create the main connector file first:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →
claude-sonnet-4-5-20250929Compare side by side →