Prevent History Addition when Main Data is Not Loaded and Ensure Proper Display Interaction

[RalfBarkow]

We need to update the History class to ensure that entries are not added to the history unless the main data is loaded and a Zettel is displayed. Additionally, the History class should interact with the Display class instead of directly with ZettelkastenView.

Tasks:

1. Update the History class to:
   • Check if main data is loaded and a Zettel is displayed before adding to history.
   • Interact with the Display class for these checks.
2. Ensure the Display class provides the necessary methods (isMainDataLoaded and getDisplayedZettel).
3. Update CRC cards to reflect these changes.
4. Write TestNG test cases to cover the new behavior:
   • Test adding to history when main data is not loaded.
   • Test adding to history when main data is loaded but no Zettel is displayed.
   • Test adding to history when both conditions are met.
   • Test avoiding duplicates in history.

Acceptance Criteria:

• History is only updated when main data is loaded and a Zettel is displayed.
• Tests cover all specified scenarios.
• CRC cards accurately reflect the new class interactions.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.