Diya fix(task addition): stabilize WBS numbering and disable DB alert on u… #4083
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the below 2 issues:
Related PRS (if any):
None
…
Main changes explained:
AddTaskModal.jsx
-- Commented out the DB update alert.
-- Compute tasksList from props.tasks (no direct Redux bind) and derive defaultCategory safely.
-- Reworked getNewNum() to use tasksList and current context (taskId, level, taskNum).
-- Recalculate WBS on modal open and when tasksList.length, taskId, level, or taskNum change.
-- Hardened null checks for allProjects.projects and tasksList to avoid .find on undefined.
ControllerRow.jsx
-- Pass the current tasks down to so numbering logic always has context.
Task.jsx
-- Forward tasks to and children; avoid directly binding tasks via mapStateToProps here.
actions/task.js
-- Keep returning the full created task object from addNewTask (callers can use _id or other fields if needed).
How to test:
npm installand...to run this PR locallyScreenshots or videos of changes:
TaskFix_DBAlert.mp4
Note:
Please refer to the video of before and after changes!