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
{{ message }}
This repository has been archived by the owner on Dec 4, 2019. It is now read-only.
This is a REST workshop, and time spent on flickering about in node.js should be reduced as much as possible. In my opinion this can be achieved by employing a HTTP framework for easier handling of routes/plan/resources, unlike the massive block of logic used in the example and starting code. E.g. Express could elevate the focus on REST and the handling of resources in this example by providing clearer routes and less boilerplate logics.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a REST workshop, and time spent on flickering about in node.js should be reduced as much as possible. In my opinion this can be achieved by employing a HTTP framework for easier handling of routes/plan/resources, unlike the massive block of logic used in the example and starting code. E.g. Express could elevate the focus on REST and the handling of resources in this example by providing clearer routes and less boilerplate logics.
The text was updated successfully, but these errors were encountered: