Skip to content

Latest commit

 

History

History
110 lines (81 loc) · 7.33 KB

README.md

File metadata and controls

110 lines (81 loc) · 7.33 KB

logo

CI / CD pipeline Quality Gate Status Coverage

Code Smells Duplicated Lines (%) Technical Debt

Vulnerabilities Maintainability Rating Reliability Rating Security Rating

What is Krafted?

A clean, decoupled and extensible, carefully crafted set of libraries for general purpose.

Krafted provides a toolkit of useful and reusable pieces of code, in order to increase your productivity. 🚀

It’s reliable, 100% documented and highly test code coverage. ✅

Why another library?

There is a problem in toolkit development, especially for general purpose:

As toolkits get new features, naturally, they get more dependencies on other 3rd packages, and when we install these toolkits, we end up relying on a number of nuget packages that we don't need, which causes unnecessary coupling, and in the worst case dependency conflict.

Well, this problem doesn't just happen with toolkits. Remember System.Web.dll? This assembly, over time, became a large monolith that contained several ASP.net (full framework) modules.

In fact, one of the problems that were solved by the .NET team through the new .NET Core / ASP.net Core, was precisely the granularization of the modules, thus solving problems such as the old System.Web.dll monolith.

When looking at the architecture and fine-grained distribution strategy of the .NET Core and ASP.net Core packages, I came up with the idea of creating a toolkit with this fine-grained strategy, providing high decoupling, independent evolution, and long life to the modules.

Another way to solve this problem would not be to create several toolkits, each one with a specific purpose?

In fact, and if you look at every Krafted package, you'll see that it's just that. Each package is independent and has a very specific purpose. However, I wanted to keep all packages under the same umbrella of the Krafted project, because in addition to being high-decoupled, Krafted has other quality criteria, and all its packages are consistent with them:

Getting started

Check out the docs to get some samples of how Krafted can help you.

To get more details, check out the API reference.

Features / where can I get?

As explained above, Krafted consists in a set of fine-grained modules, each one is delivered as a nuget package.

So get the packages according to the features you want:

Krafted.Guards

A set of Guard Clauses to validate method arguments, in order to enforce defensive programming practice.

Nuget Nuget

Krafted.Extensions

A set of extension methods for String, Collections, Guid and other types.

Nuget Nuget

Krafted.ValueObjects

A set of common Value Objects, with comparison and shallow copy operations.

Nuget Nuget

Krafted.DataAnnotations

A set of DataAnnotations attributes for validations.

Nuget Nuget

Krafted.UnitTests

Extension methods, DataAnnotations and Test Doubles to enhance the unit tests.

Nuget Nuget

Krafted.Net

A set of utility components for network operations.

Nuget Nuget

Krafted.DesignPatterns

A set of building blocks and participants to implement Design Patterns of GoF and others.

Nuget Nuget

How can I get help?

If you have a question, I suggest Stack Overflow as the fastest way to get help.

For bugs, issues or feature requests, please, create a GitHub Issue.

How can I contribute?

Annoyed for copying and pasting your utility code between your projects? 😩

How about being able to reuse your code through the Krafted? 😎

Krafted was created to be a home of useful and reusable pieces of code for the .NET community. So if you have any code snippet that is useful, clean, decoupled and tested, and want to contribute to this goal, please make a pull request! 💜