Skip to content

Fix content management #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
Aug 2, 2025
Merged

Fix content management #57

merged 14 commits into from
Aug 2, 2025

Conversation

fulleni
Copy link
Member

@fulleni fulleni commented Aug 2, 2025

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

fulleni added 14 commits August 2, 2025 21:45
- Add new event to update BLoC with the latest shared data
- Include countries list in the event properties
- Update event class with necessary overrides
- Implement CreateHeadlineDataUpdated event handling in CreateHeadlineBloc
- Update state with new country data when CreateHeadlineDataUpdated event is triggered
- Add new event to update BLoC with latest shared data
- Include countries list in the event properties
- Implement EditHeadlineDataUpdated event handler in EditHeadlineBloc
- Update constructor to listen for EditHeadlineDataUpdated events
- Add logic to update state with new country data when received
- Implement CreateSourceDataUpdated event to update BLoC with shared data
- Add handler for CreateSourceDataUpdated event in CreateSourceBloc
- Update countries and languages in CreateSourceState using new event data
- Implement EditSourceDataUpdated event to update BLoC with latest shared data
- Add handler for EditSourceDataUpdated event in EditSourceBloc
- Update state with new countries and languages data when event is triggered
… headline page

- Remove direct state access to allCountries in ContentManagementBloc
- Use BlocListener to update CreateHeadlineBloc when allCountries change in ContentManagementBloc
- Simplify CreateHeadlineBloc initialization by directly reading allCountries from context
- Add loading indicator for country data in ContentManagementBloc
…ountry data

- Remove direct state access for allCountries in EditHeadlinePage
- Implement BlocListener for ContentManagementBloc to update countries data
- Refactor widget tree to include new BlocListener
- Remove direct access to ContentManagementBloc state for country and language lists
- Use BlocListener for ContentManagementBloc to update EditSourceBloc with new data
- Add EditSourceDataUpdated event to handle updated country and language lists
- Maintain existing functionality for source editing and status updates
- Move country and language data fetching logic to BlocListener
- Update CreateSourceBloc with latest data from ContentManagementBloc
- Enhance code readability and maintainability
- Reduced code complexity in _CreateHeadlineViewState class
- Removed redundant closing parentheses to improve readability
- Adjust indentation in the buildBlocListener method
- Ensure consistent formatting for better code readability
- Reorganize import statements for better clarity
- Consolidate repeated code into functions to reduce duplication
- Adjust indentation and spacing for consistent formatting
- Refactor some widget builds for better readability
@fulleni fulleni merged commit bb79b70 into main Aug 2, 2025
1 check failed
@fulleni fulleni deleted the fix-content-management branch August 2, 2025 21:34
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @fulleni, I'm Gemini Code Assist1! 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 refactors the content management system to improve how shared data, such as lists of countries and languages, is managed and updated within the application's BLoC architecture. The primary goal is to ensure that forms for creating and editing headlines and sources always reflect the most current shared data reactively, addressing a potential issue where these lists might become stale. This is achieved by introducing a new event-driven mechanism for data synchronization, making the content management forms more robust and responsive to underlying data changes.

Highlights

  • New Data Update Events: I've introduced new DataUpdated events (e.g., CreateHeadlineDataUpdated, EditSourceDataUpdated) for all content management BLoCs. These events are designed to carry updated lists of shared data, such as countries and languages, into the BLoCs.
  • Reactive Data Handling in BLoCs: Corresponding _onDataUpdated handlers have been implemented in CreateHeadlineBloc, EditHeadlineBloc, CreateSourceBloc, and EditSourceBloc. These handlers process the new DataUpdated events, allowing the BLoCs to reactively update their internal state with the latest shared data.
  • UI Integration with BlocListener for Reactive Updates: The UI pages (create_headline_page.dart, edit_headline_page.dart, create_source_page.dart, edit_source_page.dart) now use BlocListener to observe changes in the ContentManagementBloc's state. When the allCountriesStatus or allLanguagesStatus indicates success, the appropriate DataUpdated event is dispatched to the specific BLoC, ensuring data synchronization.
  • Streamlined BlocProvider Initialization: I've streamlined the initial BlocProvider creation in the UI pages by removing the direct passing of allCountries and allLanguages. The BLoCs now rely on the new event-driven mechanism for receiving and updating this shared data, making the setup cleaner and more robust.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request effectively addresses a data synchronization issue in the content management section. By introducing ...DataUpdated events and using BlocListener to update child BLoCs when shared data is fetched, you've ensured that the UI for creating and editing headlines and sources will correctly reflect the latest available data for dropdowns. The changes are consistent and well-implemented across all affected files. My feedback focuses on improving the readability of a complex conditional logic in the listenWhen property, which is duplicated in two of the view files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant