You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@vchu22 I see no reason to, there's already a separate repo for the server-side (here). Putting webservices into a separate repo just further fractures the overall codebase, plus the end state won't be large enough to warrant using a submodule repo.
@Murkantilism Since the server-side code is written in Flask but we want the webservice to be written in Node.js, do we want to write Python code that automatically start the Node.js server when we start the Flask server?
And I saw the Flask code already has an API route named /create_survey_response. How is our Node webservices going to do differently from the /create_survey_response route?
@vchu22 to your first question - no I don't think we need to autostart the Node server
To the 2nd question - going with your example, something in this codebase needs to POST survey data to the /create_survey_response server route. A nodejs webservice is a good choice for doing that, rather than doing it directly on frontend.
Create a Node JS webservice to accept Tripetto submissions and write results to database.
Here is sample of the JSON output from Tripetto:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: