All Classes and Interfaces

Class
Description
Context for registering an admin user.
Context for listing available events starting from today.
Represents a box office for selling and refunding event tickets.
Exception thrown when attempting to register an event scheduled for a past date.
Marker interface for contexts within the application, aligning with DDD and Clean Architecture principles.
A mock implementation of the EmailService interface used for testing purposes.
 
Exception thrown when attempting to register an email that already exists in the system.
Represents an email document, including metadata and the body content.
Represents the metadata of an email, including sender, recipient, and subject.
Interface for sending emails within the application.
Represents a generic entity within the domain.
Represents the unique identifier for an entity within the domain.
Represents an evaluation of an event, including the event ID, author ID, and comment.
 
Represents an event with its poster, box office details, and evaluations.
Exception thrown when attempting to register an event that is already registered.
Context for evaluating an event.
 
Represents the information required for an event, including the title, description, and schedule.
Represents constant information for the Event Management Business, including email, CNPJ, and company name.
Context for registering an event.
Interface for managing Event entities.
In-memory implementation of the Events repository.
Implementation of the Events repository using JSON for persistence.
Represents an HTML element with tag, content, attributes, and closure information.
Exception thrown when an operation is attempted on a user that does not exist.
 
 
Context for listing tickets owned by a user.
Represents the login information for a user, including email and password.
Represents the login information for a user, including email and password.
Represents a participant in a transaction, including email, name, and tax ID.
 
Represents the details of a payment, including the payment method and amount.
Represents a payment method with details, and provides HTML representation for display.
Exception thrown when a user attempts to perform an operation without the necessary permissions.
Represents a person with a name and CPF.
Represents the personal information for a user, including name and CPF.
Represents an event poster with a title, description, and schedule date.
Represents a purchase transaction, including buying and refunding tickets.
 
Manages the creation of purchase and refund emails.
Manages the session state for a logged-in user.
Exception thrown when an event is sold out.
Represents a ticket for an event, including event ID, price, and availability.
Context for buying tickets for an event.
Context for processing ticket refunds.
Represents a transaction including payer, recipient, payment details, and description.
 
 
Represents a user, including login details, personal details, and purchased tickets.
Context for editing user details.
 
Context for managing user login operations.
Allows registering a User into a Repository.
Interface for managing User entities.
In-memory implementation of the Users repository.
Implementation of the Users repository using JSON for persistence.