Release/v8 #185
Open
Release/v8 #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update quick fix
Update qodana.yaml
…0656 🤖 Apply quick-fixes by Qodana
…8543 🤖 Apply quick-fixes by Qodana
FLR-15 Move Flames branding from author to footer
FLR 17 - Start work on Amiguito
Refactored project to JDK 20, modified user consent actions, enhanced user data storage, and fixed 'hootenanny' spelling inconsistencies. Added new data management classes and adjusted localization files accordingly.
Introduce the `HootenannyDataManager` to manage hootenanny data, including methods to save and retrieve this data. Modify `FlamesServer` and `Conversation` classes to incorporate hootenanny data operations, ensuring that relevant data is persisted correctly. A new method in `FlamesServer` checks if today is a hootenanny day.
Removed the entirety of the Amiguito feature from the codebase, including related classes, data management, and frontend components. This declutters the project by eliminating unused functionalities.
Removed obsolete `Personality` and `Thought` related classes. Transitioned user data handling to utilize `LegacyFlamesUser` and associated legacy classes, ensuring backward compatibility and maintaining data integrity during the upgrade process.
Removed legacy user handling across multiple classes and replaced it with the updated FlamesDataManager. This includes adding methods for user and server data management, refactoring interfaces to use FlamesUser, and streamlining the Conversation processMessage logic.
Replaced `LegacyFlamesUser` with `FlamesUser` in multiple commands and handlers to streamline data operations. Deleted `GetAlongCommand.java` as it was deprecated. Added getters and setters for improved encapsulation in `Conversation.java`.
Added DataUpgradeUtil to handle the migration from legacy data structures. Refactored the FlamesServer and FlamesUser classes to include constructors for compatibility with legacy data objects. Updated FlamesDataManager to save the new data structures.
Restored URL filtering in `MessageEvent`. Added methods and documentation for `FlamesDataManager`. Simplified ordinal day logic and updated several strings in resources.
Refactored the data upgrade mechanism to run conditionally based on a command-line argument "RunUpgrade". Added unit tests for FlamesServer and FlamesDataManager. Enhanced existing classes with comprehensive Javadoc comments.
Added conditions to ignore specific messages in `MessageEvent` and handled long questions in `SparkCommand`. Adjusted several text resources, included server score updates, and improved user and server data embeds to reflect changes in data handling and aesthetics.
Replaced calls to user.getName() with user.getGlobalName() across multiple classes. This change ensures that the global name is consistently used throughout the application.
Update user name method calls to use getGlobalName()
Refactored CLASSPATH definitions in various scripts to remove SNAPSHOT suffixes and organize dependencies. Introduced new user management features including destructive dropdowns and confirmation modals for data deletion, with corresponding locale properties for both English and Spanish.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.