🚀 Feature Proposal
Modularize the SharpHelpers project into multiple NuGet packages based on logical domains (e.g., Strings, Booleans, Enums, etc.), instead of maintaining a single monolithic library.
📦 Suggested Package Structure
Split the existing helpers into clearly separated libraries:
src/
├── SharpHelpers.Core/ # Optional: shared abstractions (if needed)
├── SharpHelpers.Strings/ # StringHelper.cs
├── SharpHelpers.Enums/ # EnumHelper.cs
├── SharpHelpers.Booleans/ # BooleanHelper.cs
└── ...
Each package can be published independently to NuGet, e.g.:
SharpHelpers.StringsSharpHelpers.BooleansSharpHelpers.Enums
The codebase is already small and modular, so it’s a good time to adopt a more scalable and maintainable structure before it grows further.
🚀 Feature Proposal
Modularize the SharpHelpers project into multiple NuGet packages based on logical domains (e.g.,
Strings,Booleans,Enums, etc.), instead of maintaining a single monolithic library.📦 Suggested Package Structure
Split the existing helpers into clearly separated libraries:
src/
├── SharpHelpers.Core/ # Optional: shared abstractions (if needed)
├── SharpHelpers.Strings/ # StringHelper.cs
├── SharpHelpers.Enums/ # EnumHelper.cs
├── SharpHelpers.Booleans/ # BooleanHelper.cs
└── ...
Each package can be published independently to NuGet, e.g.:
SharpHelpers.StringsSharpHelpers.BooleansSharpHelpers.EnumsThe codebase is already small and modular, so it’s a good time to adopt a more scalable and maintainable structure before it grows further.