fix: removing entry from plugin timetable updates in real-time#706
fix: removing entry from plugin timetable updates in real-time#706eduardosmaniotto wants to merge 3 commits intoMUnique:masterfrom
Conversation
Summary of ChangesHello, 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 refactors the item removal mechanism within the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
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 by creating a comment 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 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
|
There was a problem hiding this comment.
Code Review
This pull request addresses a bug in the Remove method of ValueListWrapper<TValue> by introducing a new RemoveAt method. This new method correctly handles the removal of items from both the wrapper list and the underlying data list, ensuring their consistency. The refactoring of the Remove method to use this new RemoveAt method is a good improvement. I have one suggestion regarding the implementation of the new RemoveAt method to enhance its clarity and maintainability by reordering the operations.
| this._innerList.RemoveAt(index); | ||
| this[index].PropertyChanged -= this.OnValueChanged; | ||
| base.RemoveAt(index); | ||
| for (int i = index; i < this._innerList.Count; i++) | ||
| { | ||
| this[i].Index = i; | ||
| } |
There was a problem hiding this comment.
The order of operations in this method could be improved for clarity and robustness. It's generally better to modify the primary collection (this) before the backing collection (_innerList) to maintain a more consistent state throughout the operation. Also, unsubscribing from the event should ideally happen before the item is removed from the collection.
A more logical sequence of operations would be:
- Unsubscribe the event handler from the wrapper to be removed.
- Remove the wrapper from the main list (
base.RemoveAt). - Remove the corresponding value from the inner list (
_innerList.RemoveAt). - Update the indices of the remaining items.
this[index].PropertyChanged -= this.OnValueChanged;
base.RemoveAt(index);
this._innerList.RemoveAt(index);
for (int i = index; i < this.Count; i++)
{
this[i].Index = i;
}
Update ValueListWrapper to properly implement RemoveAt:
Create a public new void RemoveAt(int index) method.
Make it remove from both _innerList and the base wrapper list (base.RemoveAt(index)).
Ensure index pointers on all subsequent wrappers are updated.
Modify existing public bool Remove(TValue item) method to use base.RemoveAt to prevent double-removals from _innerList.