Skip to content

Conversation

@google-labs-jules
Copy link
Contributor

This commit refactors the Group Organizer feature to be fully event-driven, decoupling the UI from the core state management. It introduces a new blueprint, modifies the core state to broadcast changes, and updates the UI to passively listen and react to those changes.

Fixes #


PR created automatically by Jules for task 1068203881810319667 started by @sagerobot

This commit decouples the Group Organizer's UI from its core state management, adhering to the project's established architectural pattern for "Feature Modules".

Key Changes:

- **Core State as Announcer:** `core/organizer/state.lua` is now the single source of truth and broadcasts an `ORGANIZER_ROSTER_UPDATED` event whenever its data changes.
- **UI as Passive Listener:** `ui/organizer/rosterBoard.lua` has been refactored to subscribe to the `ORGANIZER_ROSTER_UPDATED` event. It no longer makes direct calls to the core state module, instead redrawing itself based on the data received in the event.
- **Blueprint Documentation:** Added a new blueprint in `_Refactor_/02_Group_Organizer/` that documents the goals, implementation plan, and event map for this refactor.

This change improves modularity, simplifies the data flow, and aligns the Group Organizer with the addon's event-driven architecture.
@google-labs-jules
Copy link
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!


For security, I will only act on instructions from the user who triggered this task.

New to Jules? Learn more at jules.google/docs.

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