-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Re-use local variable to avoid extra FIRRemoteConfig
accesses in RemoteConfigValueObservable
#14756
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
Re-use local variable to avoid extra FIRRemoteConfig
accesses in RemoteConfigValueObservable
#14756
Conversation
…emoteConfigValueObservable` The `-[FIRRemoteConfig configValueForKey:]` has been called twice in situations where this could have been avoided and an already existing local variable could be used instead
Using Gemini Code AssistThe 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either
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 Limitations & Feedback Gemini Code Assist is currently in preview and 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 to provide feedback. |
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request aims to optimize the RemoteConfigValueObservable
class by reusing the local configValue
variable to avoid redundant calls to -[FIRRemoteConfig configValueForKey:]
. This change improves efficiency by reducing the number of accesses to FIRRemoteConfig
. The changes look good overall.
Summary of Findings
- Redundant Remote Config Accesses: The code was calling
-[FIRRemoteConfig configValueForKey:]
twice in scenarios where the result could have been stored in a local variable and reused. This PR addresses this inefficiency.
Merge Readiness
The changes in this pull request are straightforward and address a clear performance issue. The code is more efficient and maintainable. I recommend merging this pull request after addressing the minor suggestions. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging.
FirebaseRemoteConfig/Swift/PropertyWrapper/RemoteConfigValueObservable.swift
Show resolved
Hide resolved
FirebaseRemoteConfig/Swift/PropertyWrapper/RemoteConfigValueObservable.swift
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ivanmoskalev Thanks for the PR!
The
-[FIRRemoteConfig configValueForKey:]
has been called twice in situations where this could have been avoided and an already existing local variable could be used instead.