Skip to content

Add out-of-support notice pointing to StrongTypes #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
patrikmiksovsky95 merged 2 commits into from
Sep 8, 2026
Merged

Add out-of-support notice pointing to StrongTypes #178

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d2432d8
Add out-of-support notice pointing to StrongTypes
KaliCZ Sep 8, 2026
0eb4023
Don't claim EF Core and OpenAPI work with no extra work
KaliCZ Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,20 @@
# FuncSharp - Functional C#

> [!WARNING]
> **FuncSharp is out of support.** The repository is no longer maintained. The published [NuGet packages](https://www.nuget.org/packages/FuncSharp/) remain available.
>
> If you like the concepts, check out **[StrongTypes](https://github.com/KaliCZ/StrongTypes)**. It carries them forward (`Option` as `Maybe<T>`, `Try` as `Result<T, TError>`, plus `NonEmptyString`, `NonEmptyEnumerable<T>`, the numeric wrappers and intervals) with a few improvements:
>
> - Built on .NET 10 and C# 14.
> - Nullable reference types throughout: `TryCreate` returns `NonEmptyString?` rather than `Option<NonEmptyString>`.
> - Pattern matching is supported: `if (maybe.Value is { } v)` and `if (result.Error is { } e)`.
> - Generic numeric wrappers: `Positive<T>` over any `INumber<T>` replaces `PositiveInt`, `PositiveLong`, `PositiveDecimal`, …
> - The same types work end to end - in your requests, your logic and your DB models. JSON needs nothing; EF Core and OpenAPI have companion packages to install and register:
> - JSON: the `System.Text.Json` converters are attached to the types via `[JsonConverter]`, so nothing needs registering and invalid JSON fails at deserialization.
> - Database: [`Kalicz.StrongTypes.EfCore`](https://www.nuget.org/packages/Kalicz.StrongTypes.EfCore/) provides the EF Core value converters that map the wrappers to their underlying column types - see its [setup docs](https://github.com/KaliCZ/StrongTypes/blob/main/src/StrongTypes.EfCore/readme.md).
> - OpenAPI: [`Kalicz.StrongTypes.OpenApi.Microsoft`](https://www.nuget.org/packages/Kalicz.StrongTypes.OpenApi.Microsoft/) ([setup](https://github.com/KaliCZ/StrongTypes/blob/main/src/StrongTypes.OpenApi.Microsoft/readme.md)) and [`Kalicz.StrongTypes.OpenApi.Swashbuckle`](https://www.nuget.org/packages/Kalicz.StrongTypes.OpenApi.Swashbuckle/) ([setup](https://github.com/KaliCZ/StrongTypes/blob/main/src/StrongTypes.OpenApi.Swashbuckle/readme.md)) make the generated schema match the wire JSON, so generated clients get the right types.
> - Roslyn analyzers with code fixes shipped inside the package.

<p align="center">
<a href="https://mews.com">
<img alt="Mews" height="100px" src="https://user-images.githubusercontent.com/435787/129971779-2c64348e-05a3-49d0-b026-91913ffd68dc.png">
Expand Down
Loading