Fix/sync with user model update

[fulleni]

Status

READY

Description

This pull request synchronizes the in-memory authentication service with recent updates to the User model defined in the core package. It refactors user creation logic to adopt new role and access tier definitions, streamlining user attribute management and ensuring consistency across the application by explicitly overriding the core dependency.

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

[gemini-code-assist]

Summary of Changes

Hello @fulleni, 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 synchronizes the in-memory authentication service with recent updates to the User model defined in the core package. It refactors user creation logic to adopt new role and access tier definitions, streamlining user attribute management and ensuring consistency across the application by explicitly overriding the core dependency.

Highlights

• User Model Update: The AuthInmemory service has been updated to align with the new User model, replacing appRole and dashboardRole fields with role, tier, and isAnonymous.
• Feed Decorator Status Removal: The feedDecoratorStatus field is no longer initialized during User object creation in the in-memory authentication service.
• Core Dependency Override: A dependency_overrides entry has been added to pubspec.yaml to explicitly point the core package to a specific git commit, ensuring the correct version of the updated User model is used.

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 refactors the auth_inmemory package to align with an updated User model from the core package. The changes correctly adapt the User object instantiation to the new model. However, I've found a couple of areas for improvement. There's a potential logic issue in auth_inmemory.dart due to a hardcoded admin email, which could lead to incorrect role assignments if privilegedEmails are customized. Additionally, the use of dependency_overrides in pubspec.yaml could be simplified for better maintainability. My detailed comments provide suggestions to address these points.