Fix errors caused by immutable.js v4 to v5 upgrade#2458
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 addresses breaking changes introduced by an upgrade of 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
Activity
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 breaking changes from the immutable.js v4 to v5 upgrade. Most changes correctly adapt to the new, stricter typings by adding non-null assertions, nullish coalescing, or type casting. I've found a couple of places where the fix could be improved to prevent potential runtime errors. One change incorrectly casts a string to an object, which will not work as intended. Another change uses a non-null assertion that could cause a crash if an empty list is provided. My comments provide suggestions to make the code more robust.
...onents/main-page-container/main-page/side-panel/submission-form/submission-form.component.ts
Outdated
Show resolved
Hide resolved
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2458 +/- ##
==========================================
- Coverage 58.97% 58.92% -0.05%
==========================================
Files 111 111
Lines 2747 2761 +14
Branches 408 413 +5
==========================================
+ Hits 1620 1627 +7
- Misses 1065 1072 +7
Partials 62 62 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
web/src/app/components/create-survey/create-survey.component.ts
Outdated
Show resolved
Hide resolved
...onents/main-page-container/main-page/side-panel/submission-form/submission-form.component.ts
Outdated
Show resolved
Hide resolved
gino-m
left a comment
There was a problem hiding this comment.
Please also add test cases to reproduce the regression and to ensure it stays fixed.
but it was not a regression but a different immutable signature for first(). now it should be compatible with version 4 and 5. |
No description provided.