Add log information for loading and storing history items #184
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
The code changes introduce log messages to indicate when history items are being stored and loaded within the PreferencesHistoryManager. This adds a level of transparency to these processes and will aid in future debugging efforts.
dlemmermann
requested changes
May 31, 2024
gemsfx/src/main/java/com/dlsc/gemsfx/util/PreferencesHistoryManager.java
Outdated
Show resolved
Hide resolved
The logging level in PreferencesHistoryManager has been changed from info to finest. Additionally, the key related to the stored and loaded history items has been added to the log messages for more efficient debugging.
|
dlemmermann
approved these changes
Jun 3, 2024
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.
The code changes introduce log messages to indicate when history items are being stored and loaded within the PreferencesHistoryManager. This adds a level of transparency to these processes and will aid in future debugging efforts.