Some day: Multiple Packages

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
backend

Research direction

The issue discusses package boundaries for EF Core, HttpClient, and a possible Dapper integration, but names no files or tests. First read the existing package structure and the linked Dapper work in issue #3; clarify which functionality belongs in each package before estimating implementation. Done would mean an agreed package split and corresponding dependency boundaries.

Written by the indexing model from the issue text.

Description

discussion

Current version tackles EF Core and HttpClient. With #3 we will add Dapper. All of these bring with them dependencies on these other libraries. Does it make sense to have NimblePros.Metronome.Dapper as a separate package? If so, the same for EF Core and HTTP? What does that leave in the original package at that point?

Feedback welcome.

Dominant language
C#
Stars
26
Forks
0
Avg merge
12h 33m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NimblePros/Metronome

All issues in NimblePros/Metronome

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.