juspay/hyperswitch

refactor(customers):split customer related API's from to core to a submodule

Open

#1,579 opened on Jul 1, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Rust (42,690 stars) (4,676 forks)batch import
A-customersC-refactorhelp wanted

Description

Split from #1577

This will serve again as a tracking issue for the tasks the sequential tasks in customers PR...

  • #1580
  • #1581
  • #1598

Contributor guide

Tech stack
rust
Domain
backendapi
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
RustHyperswitch codebaseRefactoring patterns
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
This is a tracking issue for refactoring customer APIs into a submodule. The actual work is in sub issues #1580 (closed) and #1581 (open). Newcomers should examine #1581 to understand the concrete task. Since this issue has an assignee, it may not be available for new contributors. Look for issues labeled 'good first issue' in the repository instead.
refactor(customers):split customer related API's from to core to a submodule · juspay/hyperswitch#1579 | Good First Issue