Fix content management archive

[fulleni]

Status

READY/IN DEVELOPMENT/HOLD

Description

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[gemini-code-assist]

Summary of Changes

Hello @fulleni, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on refining the content management system by ensuring data consistency and improving the user experience, especially concerning archived content. It introduces active content filtering for creation and editing workflows, enhances the restoration process for archived items with proper state updates, and synchronizes dashboard summaries and content lists upon content modifications. Additionally, it completes the routing setup for archived content pages.

Highlights

• Content Filtering for Creation/Editing: Implemented filtering to ensure that only active content (headlines, sources, topics, countries, languages) is displayed or selectable in content creation and editing forms. This prevents users from associating new or existing content with archived items.
• Archived Content Restoration Enhancement: Enhanced the restoration process for archived headlines, sources, and topics. When an item is restored, the relevant BLoC state now explicitly includes the restored item, triggering UI updates and ensuring the main content lists are refreshed.
• Dashboard Synchronization: Added logic to automatically refresh the dashboard summary and main content management lists (headlines, sources, topics) whenever new content is created, existing content is edited, or archived content is restored. This ensures data consistency across the application.
• Router Configuration for Archived Pages: Configured the application router to correctly display the dedicated archived content pages (headlines, sources, topics) instead of placeholder widgets, making these sections fully functional.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive solution for managing archived content, including headlines, topics, and sources. The changes ensure that restoring archived items correctly updates the UI and that only active content is displayed in relevant sections of the application. The addition of filtering by 'active' status across different parts of the application (dashboard, create/edit forms) enhances correctness and user experience. The new pages for archived content are also correctly wired into the router. I've provided a few suggestions to improve code consistency and formatting. Overall, this is a solid set of changes.