-
Notifications
You must be signed in to change notification settings - Fork 4.8k
solution #5224
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
base: master
Are you sure you want to change the base?
solution #5224
Conversation
mateacademy-ai-mentor
left a comment
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.
Review Summary
Great job on implementing the core logic for the state transformation! Your function correctly handles immutability by creating clones of the state, which is a key part of this task.
However, a couple of changes are needed to meet all the project requirements. The task explicitly requires using a switch statement to handle the different action types, but your solution uses an if/else if chain [CHECKLIST ITEM #2].
Please refactor this part of your code to use a switch statement. When you do, remember to also include a default case to handle any unknown action types, as this is another requirement [CHECKLIST ITEM #3]. Once those changes are made, your solution will be perfect!
✨ Please rate this review in the Platform's notification center1. I will be grateful for your feedback! ✨
Important
Fix the issues, commit the changes, and then re-request my review using the Re-request review button2 in the Reviewers tab.
Tip
If you have any comments about this review, please leave a message in the Add a comment section below and mention me with the @mateacademy-ai-mentor tag3.
I will read your message during my next review of your pull request. Please do not reply directly to my comments, as that feature is not supported yet.
Caution
Do not close the pull request until the review is complete. Closing it early can lead to unexpected behavior and disrupt the review process.
Footnotes
src/transformStateWithClones.js
Outdated
| if (action.type === 'addProperties') { | ||
| newState = { ...newState, ...action.extraData }; | ||
| } else if (action.type === 'removeProperties') { | ||
| newState = { ...newState }; | ||
|
|
||
| for (const key of action.keysToRemove) { | ||
| delete newState[key]; | ||
| } | ||
| } else if (action.type === 'clear') { | ||
| newState = {}; | ||
| } |
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.
This violates checklist item #2: '[CODE STYLE]: Use switch statement if you have limited amount of conditions.'
You should use a switch statement to handle the different action.type values. When you refactor this, also remember to include a default case to handle unknown action types, as required by checklist item #3.
mateacademy-ai-mentor
left a comment
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.
Review Summary
Excellent work on this revision! I am approving your solution as you've successfully addressed all the feedback from the previous review. Your refactoring to a switch statement with a default case is implemented correctly, and you've done a great job ensuring state immutability is maintained throughout the function. The code is clean, correct, and meets all the task requirements. Well done!
✨ Please rate this review in the Platform's notification center1. I will be grateful for your feedback! ✨
No description provided.