Add grouped episode handling and refactor social network messaging system

[Ziedelth]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Ziedelth, 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 significantly enhances the system's ability to handle and announce new episode releases. By introducing a 'GroupedEpisode' abstraction, the application can now process and present multiple related episodes as a single unit. This change has led to a comprehensive refactoring of the social network integration, allowing for more dynamic message generation, improved media image creation for multi-episode announcements, and the addition of a configurable delay for publishing these updates.

Highlights

• Grouped Episode Handling: Introduced a new 'GroupedEpisode' entity and factory to logically group multiple episode variants or distinct episodes, streamlining their management and presentation.
• Refactored Social Network Messaging: The social network posting system has been refactored to leverage the new 'GroupedEpisode' concept, allowing for more flexible and consolidated announcements of episode releases, including support for multiple episodes in a single post.
• Delayed Social Network Posting: Implemented a configurable delay before sending episode release notifications to social networks, providing better control over the timing of announcements.
• Enhanced Media Image Generation: The media image generation service now supports creating a single, grid-based image for multiple grouped episodes, or a standard image for a single grouped episode, improving visual consistency across social platforms.
• Flexible Social Network Message Templates: Added new configuration keys and message templating capabilities for social networks, enabling distinct messages for single versus multiple episode releases, with new placeholders for richer content.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 grouped episode handling and refactors the social network messaging system. The changes are extensive and well-structured, especially the new logic in AbstractSocialNetwork for composing messages for single or multiple episodes. The introduction of a delay before sending notifications is also a good addition for handling bursts of new episodes. However, there are several critical and high-severity issues related to the unsafe use of the not-null assertion operator (!!) on nullable properties, which could lead to runtime crashes. I've pointed these out with suggestions for safer alternatives. I've also noted a few medium-severity issues regarding code style and unnecessary code. The addition of tests for the new messaging logic is a great practice.