V4.2.3

📅 DisCal Release 4.2.3

This release cleans up some minor UX issues observed, and begins substantial work on refactoring DisCal's legacy code to support modern best practices in a healthy piece-meal application, allowing me to continue to fix bugs and add new features while progressing through the code cleanup.

Milestone: 4.2.3

⭐️ New Features and Additions

• When changing an event's start/end in the event wizard, there is now the option to keep the overall length of the event by automatically adjusting its start/end.
  • This can be done with the new optional command argument keep-duration:true/false in the /event start and /event end commands.
  • Or can be set globally with /settings keep-event-duration command. This can always be overridden when use the start/end commands.

🪄 Improvements

• Cleaned up Gradle build files. #142
  • This will allow me to more easily manage dependencies and reduce how many deps DisCal needs.
  • Makes builds more repeatable and less fragile
• Upgraded Spring Boot framework & began work on moving to Spring Data (data access refactor) #142
• Setup Docker compose allowing me to iterate much faster and test locally with a clean env every time. #142
• Removed guild members intent.
  • This intent is no longer needed now that all commands have been moved to slash commands, so this intent can finally be removed.
• Began work on refactoring to using Kotlin Coroutines and Spring DI properly #146

🐞 Bug Fixes

• Fixed some arrant Kotlinx serialization errors

🔨 Work in Progress and Upcoming Changes

• Refactor to kotlin coroutines for actually maintainable code
• Phasing out legacy data access patterns

💜 Thanks

Thank you to everyone who has helped contribute to DisCal! This project would not be possible without you.