🚨Announcement🚨

A new, version (2.1.0) of FluentContracts is LIVE!

We have brand new contracts available for "FileInfo", "DirectoryInfo", "Dictionary" and more!

Go, check it out!

Pls share 🙏

#dotnet #fluentapi

https://github.com/FluentContracts/FluentContracts

🚨 Announcement 🚨

A new, major version (2.0.0) of FluentContracts is LIVE!

Some refactoring + some new cool contracts:

- String.BeCreditCardNumber
- String.BeBase64
- DateTime.BeInThePast/Future
- DateTime.BeWeekend

Pls share🙏

#dotnet #FluentAPI

https://github.com/FluentContracts/FluentContracts

🚨 Announcement 🚨

FluentContracts v1.4.0 has been released!
https://github.com/FluentContracts/FluentContracts/releases/tag/1.4.0

This version includes cool new "string" contracts like:
- BeEmailAddress - kudos to @matkoch
- BeIpAddress
- BeAlphanumeric

... and more!
And I am just getting started. Tons of others are in the making.
#dotnet #fluentapi

👋 Hey folks!

✅ Version 1.3.0 of FluentContracts was just released!
The library for fluent argument validation in #dotnet

🎉 Go check out all the cool contract types that were added!

https://github.com/FluentContracts/FluentContracts/blob/develop/CHANGELOG.md

I am thrilled to announce my first #OSS #dotnet project of my own:

FluentContracts!
"Fluent argument validation for fluent software development"
https://github.com/FluentContracts/FluentContracts

I am excited to start this journey and I want to ask everyone for feedback and pointers on what I am doing right or wrong. 🙏

What is your take on the #monorepo paradigm when talking about 100-ish services? 🤔

✅ Is it good?
❌ Is it bad?

Would you use it for non-monolithic architecture?

Any input and RT would be appreciated, so I can gather as many viewpoints as possible. 🙌