v1.3.1

This release request introduces a significant expansion and refactoring of the application's fixture data. The core change involves adding a mandatory logoUrl property to the Source model, which necessitated updates across existing fixtures and the addition of a wealth of new mock data for various content types. This enhancement aims to provide a more comprehensive and realistic dataset for testing and development purposes, ensuring better representation of diverse news sources and user preferences.

Highlights

• Breaking Change: Source Model Update: The Source model now includes a new required property, logoUrl, to store the URL of a source's logo. This is a breaking change and has been reflected in the CHANGELOG.md.
• Expanded Fixture Data: A significant amount of new fixture data has been added across various categories, including new Source IDs (up to 90), Headline IDs (up to 450), and SavedFilter IDs. This greatly expands the available mock data for development and testing.
• Source Fixture Enhancements: All existing Source fixtures have been updated to include a logoUrl, utilizing Clearbit for dynamic logo URLs. Numerous new Source fixtures have been introduced, covering local, national, international, specialized, blog, government, and aggregator types.
• Headline Fixture Additions: A large set of new Headline fixtures have been created, providing diverse content for the newly added sources. Each new source now has multiple associated headlines.
• User Content Preferences and Saved Filters: The userContentPreferencesFixturesData has been updated to include new followed sources (San Francisco Chronicle, ESPN) and several new SavedFilter fixtures (Global Sports, Science News, Political News) for the first user.

v1.2.1

This release streamlines the management of fixture data by consolidating SavedFilter definitions directly within the UserContentPreferences fixture. This change simplifies the fixture setup and reinforces UserContentPreferences as the central source for user-specific preferences and presets. Additionally, the update replaces static image URLs in headline fixtures with dynamic picsum.photos links, enhancing the realism of the placeholder content.

Full Changelog: v1.2.0...v1.2.1

v1.2.0

Introducing User-Defined Content Presets & Architectural Refinements

This release focuses on enhancing user personalization by introducing the ability for users to save and manage their own content filters. To support this significant new feature, we've also made several structural improvements to the data models, ensuring the architecture remains clean and maintainable for future development.

💾 Saved Content Filters

This release introduces a powerful new capability for end-users: saved filters. The core goal is to allow users to create, store, and reuse complex filter combinations, streamlining their ability to access the news content that matters most to them.

• ✨ Introduces the SavedFilter data model, which allows users to store custom combinations of topics, sources, and countries for later use. [#56]
• 🔗 Integrates saved filters directly into the UserContentPreferences model as a required field, making custom presets a core part of a user's profile. [#56]
• ⚙️ Implements configurable limits on the number of saved filters a user can create, with distinct tiers for guest, authenticated, and premium users. [#56]

🏗️ Model Refinements & Maintenance

To properly support the new saved filters feature and improve overall code quality, we've refined the project's structure. These changes enhance maintainability and ensure our testing and documentation remain robust and up-to-date.

• 🗂️ Reorganizes all user-preset data models into a new, dedicated user_presets directory, improving overall code structure and clarity. [#56]
• 🧪 Adds comprehensive unit tests for the new SavedFilter model and updates all related test fixtures to ensure reliability and consistency. [#56]
• 📄 Updates the project's documentation to accurately reflect the new data models and the addition of the "User Presets" functionality. [#56]

---

For a detailed summary of changes, see the Technical Changelog.