• For the creation of technical events in a company, it was requested to create an Event System that allows centralizing the data of all events, controlling the vacancies available, and conducting evaluations after the end of the event. The registration of events will be done through the application itself, any user will be able to register, respecting the limit of available places.
• Para a criação de eventos técnicos em uma empresa, foi solicitado a criação de um Sistema de Eventos que permite centralizar os dados de todos os eventos, controlar as vagas disponíveis, e realizar a avaliações após a finalização do evento. O cadastro de eventos será feito através da própria aplicação, qualquer usuário poderá se inscrever, respeitando o limite de lugares disponíveis.

• 1. REGISTER AN EVENT

  • Administrative users must have access to functionality to register a new event
  • Each Event must have the following fields:
    • Name
    • Start date / time
    • End Date / Time
    • Location (text field)
    • Description
    • Limit of places
    • Category
  • RULES:
    • All fields of the string type are mandatory and must respect the maximum character limit
    • Date / time fields are mandatory, the date of the event must be greater than today's date, and all events must begin and end at same day
    • Category is should be a listing of the available categories.
    • Every event will have a status field, which will not be displayed at creation, but that must be defined at creation, the default value will be: “Open for Registrations".
    • The status must have the following possible values: “Open for subscriptions "," In progress "," Completed "and" Canceled".

• 2. MANAGE AN EVENT

  • Only administrative users should have access to this functionality, the administration should allow:
    • Cancel the event.
    • View a list of participants (people who signed up for the event).
    • Indicate that a participant was present at the event.
    • Start the event.
    • Complete the event.
  • RULES:
    • On the day of the event it will not be possible to cancel it.
    • It will only be possible to start the event on the start day.
    • The functionality to complete the event will only be released after the event has started.
    • Only after the event has started will it be possible to indicate whether a participant is present at the event.

• 3. LIST AN EVENT

• All users must have access to the list of all available events, in the event view the status of the event must be indicated.

• It must be possible to search the event by category (list of options) and by date of the event.

  • RULES:
    • The comparison of dates should only consider the day, it should not consider the time of the event.

• 4. VIEW DETAILS OF AN EVENT

• All users must have access to the details of an event, where it will be possible sign up for the event, or make your assessment.

  • RULES:
    • It will be possible to register for the event, only if there are vacancies available.
    • After the end of the event, if the person has attended (indication by the administrative user), the option to evaluate the event will be released, through comment note.

• Open the .sln file in a Visual Studio IDE
• Build the project and execute
• Complete the final url with /swagger, some like https://localhost:44360/swagger/index.html
• See the endpoints of the project!

That's it for today. See you later! 👋👋