juspay/hyperswitch

[FIX] separate crate specific settings from `settings.rs` to their respective crates

Open

#1,563 opened on Jun 28, 2023

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Rust (42,690 stars) (4,676 forks)batch import
A-frameworkC-refactorgood first issuehelp wanted

Description

Separate and split crate specific implementation into their own crates, example of such are:

  • Move database configuration to storage_models
  • Move redis configuration to redis_interface

Contributor guide

Tech stack
rust
Domain
backendinfrastructure
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingCrate structure in Hyperswitch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current settings.rs file in the Hyperswitch repository to identify database and Redis configuration sections. Then, locate the storage models and redis interface crates to determine how to move the relevant configuration into each crate, ensuring proper module declaration and import paths. Review any existing comments or PRs for additional context, such as the assignee's progress or maintainer guidance.