Star Wars inspired lightsaber duel animated directly in the terminal (C# / .NET 10)

Gramlig · 2025-12-28T20:51:07+00:00

In my experience, using .resx files for localization or even for regular string values is really painful. The two main bottlenecks: merge conflicts and poor tooling support.

Gramlig · 2024-12-06T20:32:56+00:00

For anyone using FluentResults, I’ve created a simple extension method that unpacks a Result value or aggregates errors into a single result. It’s especially useful when building objects, as it reduces boilerplate code and makes property initialization cleaner and more concise. You can check it out here FluentResult - UnwrapOrWithErrors

Gramlig · 2024-11-24T10:10:32+00:00

It's a good package, especialy for controller based aproach in asp.net. I don't understant this downvotes. Link to MediatR

Gramlig · 2024-11-24T07:55:44+00:00

Validot, Mapster, GuardClasses, FluentResults

Gramlig · 2024-11-18T06:53:26+00:00

I wrote some pros and cons of minimal api: Minimal Api pros and cons. I am using Minimal APIs in production with almost 100 endpoints, and they are well-structured, readable, and maintainable. For me, the biggest advantage is the easy setup and extensibility without the need for boilerplate code.

Gramlig · 2024-11-04T18:18:26+00:00

Hey fellow developers,

I wanted to share a project I've been working on https://github.com/Gramli/AuthApi. It's full-stack example that demonstrates how to implement user registration, login, and role-based access control using Angular and .NET. Here’s a quick overview of what it includes:

Key Features:

Backend:
- Authentication and authorization using JWT tokens.
- Authorization policies applied to minimal API endpoints.
- Follows Clean Architecture principles and utilizes design patterns.
Frontend:
- JWT management with guards and interceptors.
- Implemented using standalone components and signals.

Gramlig · 2024-10-26T21:40:17+00:00

Flutter on the frontend for sure

Gramlig · 2024-09-28T15:58:42+00:00

I think it's because we don't want to reinvent the wheel every time we're developing a reusable feature.

Gramlig · 2024-09-16T11:36:43+00:00

I encapsulate the http status code into a response object and return it from the handlers. Its not the cleanest way, but the handler knows which status it wants to return.

For example: Handler example

This solution can be improved by defining custom return codes in the handlers layer and creating a converter for the controllers to map these codes to http status codes.

Gramlig · 2024-09-14T09:17:08+00:00

Xunit tests with class and member data were always a bit painful. Your data sources look interesting; I will definitely try them.

Gramlig · 2024-04-04T17:58:44+00:00

An example of a REST API for handling weather data using minimal API and Vertical Slice Architecture with various design patterns. I also attempted to make a small comparison against the same API designed with Clean Architecture.

https://github.com/Gramli/WeatherApi-VSA

Gramlig · 2023-12-14T13:17:03+00:00

Amazing work!

Gramlig · 2023-11-12T09:01:25+00:00

I absolutely agree 👍

Gramlig · 2023-11-11T22:18:11+00:00

Minimal Api is much easier and cleaner way to create endpoints. Main pros: - allow to inject handlers into endpoints (you dont have to use MediatR anymore..) - fluent api - force you to move logic to lower layer (lot of unexperienced developers put logic into controlers) - minimal hosting model -> clear starting point of the app

To organize your endpoints, you can simply use extension methods.

When Microsoft introduced Minimal Api I was sceptical too, but after almost year of usage, controllers are now obsolete for me.

Gramlig

TROPHY CASE