Fix recommendation form fetch flow and API handling#507
Fix recommendation form fetch flow and API handling#507jayapattar20-tech wants to merge 4 commits into
Conversation
|
@jayapattar20-tech is attempting to deploy a commit to the komalsony234-1530's projects Team on Vercel. A member of the Team first needs to authorize it. |
komalharshita
left a comment
There was a problem hiding this comment.
Thanks for fixing the duplicated fetch flow and malformed promise chain — this resolves a real issue currently present in main.
Before merge, please make a few small cleanup changes:
- Remove temporary debug logs (console.log, raw console.error) from renderResults()
- Avoid silent try/catch blocks around card rendering unless fallback UI/error handling is added
- Keep the diff focused on the fetch/API flow cleanup only
After these small refinements, this PR should be good to merge.
|
Hi @komalharshita , |
|
Looks good to merge....but you need to resolve the conflicts @jayapattar20-tech |
|
Hi, @komalharshita |
|
@jayapattar20-tech please check again |
Summary
Fixed the recommendation form fetch flow and improved frontend API handling for project recommendations. Resolved JavaScript promise chain issues and removed console errors caused by incorrect fetch/catch structure.
Related Issue
Closes #416
Type of Change
What Was Changed
static/script.jsstatic/script.jsstatic/script.js.then()/.catch()flowHow to Test This PR
git checkout fix-view-code-buttonpip install -r requirements.txtpython app.pyTest Results
(Attach your test output here if you ran tests)
Notes for Reviewer
Recommendation data is successfully fetched from the backend API and frontend fetch flow issues were resolved. Further UI rendering behaviour may depend on existing frontend card rendering structure/components.