Skip to content

Some day: Multiple Packages #9

@ardalis

Description

@ardalis

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions