nammayatri / nammayatri/shared-kernel
Move external integrations from shared-kernel dependency to current codebase
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 24
- Forks
- 11
- Avg merge
- 15h 16m
- Merged PRs (30d)
- 35
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or specific integrations. Start by locating the shared-kernel dependency and the external integrations it contains; clarify which current codebase should own them and define completion as those integrations no longer being sourced from shared-kernel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100