Loading repository data…
KUTlime / repository
> A minimal, non-syntetic, clean architecture, modern C# 11 syntax, feature rich demo application for checking stock prices.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
A minimal, non-synthetic, clean architecture, modern C# 11.0 syntax, feature rich demo application for checking stock prices.
.editorconfig for modern, compact C# syntaxTo solve circular dependency problem. The infrastructure logic could be either in the application layer or in the separate layer with abstractions from the application layer.
The first solution violates the Separation of Concerns principle (application is directly depended on the infrastructure). The latter produce the circular dependency problem.
To overcome this problem, the cross concerns layer is introduced. The presentation layer has to link two layers: the application & the cross concerns layer.
These classes represents API-provider contract. This is an implementation detail of API providers. The services provides their own DTOs. Hence, they are not used anywhere else outside the scope of service methods. The only reason why they are not private is to facilitate null flow and API consistency checks. The generic contract check methods are introduced. They have to have an access to these nested classes. The contract check methods provides a systematic approach to 3rd party contract control.
The use of enum is a violation of Inversion of Control principle. You can't deploy the presentation layer without redeploying the application layer. To fulfil this principle, one must pass an abstract object (e.g. string). Yes, this is a violation of type safety but this trade off could be compensate by unit testing.
editorconfig has IDE0058 turn on?This rule can be annoying at the beginning, but eventually, it provides a real value. I learned that on multiple occasions.
See this code
private static void RegisterFinnhubServices(IServiceCollection services)
{
services.AddScoped<IHttpClient, FinnhubHttpClient>();
services.AddScoped<IStockProvider, FinnhubStockService>();
services.AddScoped<IStockNameProvider, FinnhubStockNameService>();
services.AddScoped<IToken, FinnhubTokenId>();
}
Looks normal, cool if you like, right? Actually, no. It can be simplified into
private static void RegisterFinnhubServices(IServiceCollection services) =>
services.AddScoped<IHttpClient, FinnhubHttpClient>()
.AddScoped<IStockProvider, FinnhubStockService>()
.AddScoped<IStockNameProvider, FinnhubStockNameService>()
.AddScoped<IToken, FinnhubTokenId>();
You will not see this without IDE0058 turned on.
And yes, it's perfectly clear to me that you may find the first form better and more readable. In that case, this repo (or at least my .editorconfig) is not for you.
Selected from shared topics, language and repository description—not editorial ratings.
Cassisilverston /
Minimal API de alta performance para Gestão de Frotas. Implementada com .NET 10 (LTS), C# 14 e Clean Architecture. Inclui autenticação segura via JWT, PostgreSQL (Neon) e documentação interativa com Scalar.
46/100 health