NuGet packages per transport

Open
  • Is something wrong?
#24 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
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
build-system

Research direction

Start by reading the repository's package and release configuration, especially the release-please setup and transport project structure. The issue calls for one NuGet package per transport so apps can install only the broker client they use; done means transports can be packaged and released independently.

Written by the indexing model from the issue text.

Description

enhancement

release-please and one package per transport, so an app only pulls the broker client it uses.

Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 4m
Merged PRs (30d)
8

Getting set up

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 softvasco/outbox-kit

All issues in softvasco/outbox-kit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.