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
Rendering update #8
Conversation
Co-authored-by: JeanCGedeon <JeanCGedeon@users.noreply.github.com> Co-authored-by: Tyler <br.ndt.tyler@gmail.com> Co-authored-by: camziny <camziny@users.noreply.github.com>
fix front-end post request for reviews (added userId in state) merge attractionReviewsRouter merge from 4232cef Co-authored-by: Tyler <br.ndt.tyler@gmail.com> Co-authored-by: camziny <camziny@users.noreply.github.com>
} catch (error) { | ||
return res.status(500).json({ errors: error }); | ||
} | ||
}); |
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.
user id should come from your passport session, via req.user
, not from the frontend.
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.
there is also no ValidationError handling here. You are handling for these types of errors on the frontend, but in this implementation those errors would never be used
add locationAttractionsRouter remove placeholders from forms incorporate user session data add authenticated routes for forms add Location dropdown to NewAttractionForm Co-authored-by: JeanCGedeon <JeanCGedeon@users.noreply.github.com>
fix fetch request on the front-end
add userId into state on the front-end
edit the top bar
add attractionReviewsRouter(also update userId in the post request)