-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Document the LoopBack 4 request-response cycle #1833
Comments
@hacksparrow , I can't wait to see this documentation. I am hungry to learn. |
based on @raymondfeng's feedback, here are some details to consider in this narrative (opt for visualization for clarity):
Try to group it into two phases: 1st phase interaction between API client and LoopBack, 2nd phase API business logic interact with existing backend services using repositories/datasources/models. |
Closing as duplicate of #2390 |
@dhmlau I slightly disagree. The goal of #2390 is to describe request-handling flow at high level, especially in regards to different Express middleware types. I am concerned that by including low-level details listed in #1833 (comment), we will greatly inflate the scope of #2390. Was this change taken into account when #2390 was estimated? |
When discussing with @raymondfeng , he mentioned that this is a duplicate of #2390. Since #2390 has more descriptions so we're closing this issue instead. @raymondfeng , what's your thoughts? |
Let's reopen it for now so that we won't forget. |
I would start with #2390, I think it's a smaller task. |
FYI - There's a diagram at the top of https://loopback.io/doc/en/lb4/Concepts.html, it would be a good starting point. https://loopback.io/pages/en/lb4/imgs/key-concepts-overview-diagram.png |
PR in progress: #4914 |
Closing this issue as #4914 lands |
This will be a low-level description of all the components involved in the request-response handling process. It will help consumers and developers interested in knowing what's happening under the hood.
The text was updated successfully, but these errors were encountered: