Diya fix(qst): add newly assigned projects to user profile#4067
Merged
Conversation
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
DiyaWadhwani
added
the
High Priority - Please Review First
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Project assignment via Quick Setup would show the new project in the projects tab and then disappear immediately on success popup.
Root cause: The frontend payload in handleSubmit overwrote the updated projects array with a stale variable, and the Assign modal sometimes sent mixed shapes (_id vs projectId), causing the backend to retain only the last item.
Fixes: (Priority: High) – The project assignment was failing in the Quick Setup flow.
Related PRS (if any):
None
Main changes explained:
-- Build the payload from the merged updatedUserProfile instead of overriding with a stale projects variable.
-- Normalize projects to a stable list of string IDs (_id or projectId) before sending to the API to avoid accidental drops.
-- Use project.projectId (with fallback if needed) when constructing links / payloads so the selected project’s id is consistent with the rest of the UI.
How to test:
npm installand...to run this PR locallyScreenshots or videos of changes:
QST_Fix.mp4