Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix/new migration to add saved filters limit to remote config #69

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

Conversation

@fulleni
Copy link
Member

@fulleni fulleni commented Oct 13, 2025
edited
Loading

Status

READY

Description

This pull request introduces a new database migration designed to dynamically manage the number of saved filters available to users, categorizing them by tier (guest, authenticated, premium). By integrating these limits into the remote configuration system, the application gains enhanced flexibility in controlling user features without necessitating new code deployments. This change ensures that the system can effectively adapt to varying user access levels for saved filter functionality.

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

- Introduce new fields for saved filters limits in remote config
- Set default values for guest, authenticated, and premium user tiers
- Implement migration to add these fields to existing documents
- Create reversible migration with up and down methods
- Add savedFilters field to user_content_preferences
- Introduce SavedFilter data model
- Implement configurable limits for saved filters based on user tiers
- Enhance user experience by allowing management of custom filter combinations for news headlines
- Implement new migration for adding saved filters to remote config
- Update all_migrations.dart to include the new migration
Copy link

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 introduces a new database migration designed to dynamically manage the number of saved filters available to users, categorizing them by tier (guest, authenticated, premium). By integrating these limits into the remote configuration system, the application gains enhanced flexibility in controlling user features without necessitating new code deployments. This change ensures that the system can effectively adapt to varying user access levels for saved filter functionality.

Highlights

  • New Migration for Saved Filter Limits: A new database migration, 20251013000057_add_saved_filters_to_remote_config.dart, has been introduced to manage limits for saved filters across different user tiers.
  • Remote Configuration Integration: The migration adds guestSavedFiltersLimit, authenticatedSavedFiltersLimit, and premiumSavedFiltersLimit fields to the remote_configs collection within the userPreferenceConfig sub-document, setting default values of 3, 10, and 25 respectively.
  • Migration List Update: The newly created AddSavedFiltersToRemoteConfig migration has been registered in all_migrations.dart, ensuring it is included in the database migration process.
  • Migration Summary Enhancement: The prSummary within the 20251013000056_add_saved_filters_to_user_preferences.dart migration file has been updated to provide a more detailed description of its purpose.
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.

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 introduces a new database migration to add limits for saved filters to the remote configuration. The changes are functionally correct, but I've identified an opportunity to improve the maintainability of the new migration file. My feedback focuses on replacing hardcoded 'magic values' (both numbers and strings) with named constants. This will make the code more readable, less prone to typos, and easier to update in the future. I've provided a detailed suggestion on how to implement this.

@fulleni fulleni merged commit 321f87f into main Oct 13, 2025
1 check failed
@fulleni fulleni deleted the fix/new-migration-to-add-saved-filters-limit-to-remote-config branch October 13, 2025 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /