kadai-io/kadai

AI Summary: Refactor the Kadai event management system to improve its design. The current implementation mixes domain logic and auditing concerns within domain services. The task requires moving the auditing logic (adding user IDs and other contextual data to events) to a dedicated orchestrator or mediator, separating concerns and improving maintainability. This likely involves creating a new component (or extending an existing one) to handle event decoration before publishing, and potentially addressing the dual use of event types as both domain and persistence types.

AI Summary: The task involves migrating the KADAI project's MyBatis queries from using `ExecutorType::SIMPLE` to `ExecutorType::BATCH` for improved performance in bulk operations. This requires modifying the existing MyBatis mapper code to leverage batching capabilities, potentially involving changes to how dynamic SQL is handled and testing the impact on performance.

AI Summary: Improve error handling in the KADAI REST API for bulk import endpoints. Specifically, create a new exception type and error code to distinguish between database insertion failures and logical duplicates in the input payload. Update affected endpoints to return a 400 BAD REQUEST status code with the new error code when logical duplicates are detected. Thorough testing is required to ensure the new behavior is correctly implemented and existing tests are adjusted.

AI Summary: The task involves reviewing and correcting the copy constructors throughout the KADAI Java library's codebase. This includes ensuring all necessary fields are copied by value (not by reference) and that no required fields are omitted in the copy constructor implementations. The goal is to ensure that creating copies of objects results in independent, correctly initialized objects.