Event pipeline #87
Event pipeline #87
Conversation
…ll as its minimum/maximum price for a ticket
| DateTime StartDate, | ||
| DateTime EndDate, | ||
| uint? MinimumAge, | ||
| List<GetEventResponseCategoryDto> Categories, |
There was a problem hiding this comment.
Here we mix DTOs from GetEvent andGetEventDetails. I dont say it is wrong but shouldn't we create a GetEventDetailsResponseCategoryDto? I know it will be the same think but it looks like something that you would comment me on. It is more a question.
There was a problem hiding this comment.
I think it can stay this way? The thing is, usually we want to separate DTOs, even with the same content, for the possibility that one of them will need to change (which is especially important in request DTOs as we usually want to change parameters of one endpoint at a time). Here, I can't really think of a case, where we would want to have these DTOs differ (unless we add some parameter categories, which should be obstructed only in the "non-details" view, which I don't think is likely? But I'll leave the final judgement up to you, as maybe it would be more clear if these were separate records.
Created a pipeline allowing for getting information about a specific event, including its ticket types from the front end application as a setup for creation of the shopping cart