nadirbad / verticalslicearchitecture Goto Github PK

Hello!

I was wondering why you made the decision to group the IEntityConfiguration types in the /Infrastructure/configuration/ while everything else pertaining to the ToDoItem was in the Feature area. I would think that the IEntityConfiguration files are included in the Feature area

Hi @nadirbad, I'm wondering why you have split the code in two projects like API and Application. I would expect to see the controller in the API project, but we find it in the Application project.

Thanks!

Hello,

first of all, thank you very much for creating a template with this type of software architecture.
I downloaded the template and everything works great, but there's a problem in the integration test project with the Testing class.
The Startup class doesn't exist in the API. I understand that when you migrated it from .NET 6.0 to 7.0, this issue might have been left pending.
This is the file location: VerticalSliceArchitecture/tests/Application.IntegrationTests/Testing.cs

Thanks

Of all examples about VSA on the internet, I found this one to be the most relevant (at least from my POV, obviously), so thank you for this !

My only question is why do you use Mediator ?

Otherwise said, what is the benefit of Mediator instead of directly implementing in the controller (or in a dedicated class but without the IRequestHandler) ?

public class ExportTodosController : ApiControllerBase
{
    private readonly ApplicationDbContext _context;
    private readonly IMapper _mapper;
    private readonly ICsvFileBuilder _fileBuilder;
    
    [HttpGet("/api/todo-lists/{id}")]
    public async Task<FileResult> Get(int id)
    {
        var records = await _context.TodoItems
                .Where(t => t.ListId == request.ListId)
                .ProjectTo<TodoItemRecord>(_mapper.ConfigurationProvider)
                .ToListAsync(cancellationToken);
        var csv = _fileBuilder.BuildTodoItemsFile(records);

        return File(csv, "text/csv", "TodoItems.csv");
    }
}

Doing this you still have testability, isolation from other features / coupling inside the slice, so why bother with an additional technical component ?