GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||
GeezerVison is showing github.com — docs(aio): update architecture section by jbogarthyde · Pull Request #21569 · angular/angular Conversation
Contributor
PR ChecklistPlease check if your PR fulfills the following requirements:
PR TypeWhat kind of change does this PR introduce? What is the current behavior?Issue Number: N/A What is the new behavior?Does this PR introduce a breaking change?Other informationUpdate doc with new section on architecture.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
|
@StephenFluin - The old PR was hopelessly munged. Please review this new PR with the changes we discussed, and some of the restored content that was lost in the previous PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can preview a324941 at https://pr21569-a324941.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can preview d720ba1 at https://pr21569-d720ba1.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@jbogarthyde, can you please squash all commits into one and rebase on master? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
d720ba1 to
fdc0d52
Compare
|
You can preview fdc0d52 at https://pr21569-fdc0d52.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
(wrong PR) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hi @jbogarthyde! This PR has merge conflicts due to recent upstream merges. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hi @jbogarthyde! This PR has merge conflicts due to recent upstream merges. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
fdc0d52 to
4e9e77f
Compare
|
You can preview 4e9e77f at https://pr21569-4e9e77f.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can preview ffa43f0 at https://pr21569-ffa43f0.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I don't think #21957 is fixed with this. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can preview 4ffe4bd at https://pr21569-4ffe4bd.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This will also close issue #22158 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
5d7965b to
7ccf9ac
Compare
|
You can preview 7ccf9ac at https://pr21569-7ccf9ac.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
7ccf9ac to
784d54a
Compare
|
You can preview 784d54a at https://pr21569-784d54a.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Saying that it "uses a Promise to fetch" sounds weird.
It uses the Backend service, which in turns uses something else under the hood (e.g. XMLHttpRequest, fetch, etc.) and returns a Promise to represent the future result/response.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This section makes it sound a little bit as if DI only works on components, while it also works (and is extensively used) in other places, such as services, pipes, NgModules.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
they become accessible in all parts of the app
Not true for lazy-loaded modules, which get their own injector 😁
But maybe this simplification is fine for this introductory guide.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
added note that you can specify providers at component level (which is now preferred, since it makes them tree-shakeable).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
because other components --> because other modules
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
An NgModule has a root component, created during bootstrap
This mostly applies to the root NgModule only.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Does this work?
NgModules provide a compilation context for their components. A root NgModule always has a root component that is created during bootstrap, but any NgModule can include any number of additional components, which can be loaded through the router or created through the template. The components that belong to an NgModule share a compilation context.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Calling a "custom element" is confusing (since people might think of https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
which alters the HTML before the view is rendered
It can modify the HTML at any time, not just before the view is rendered.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Why not link to https://pr21569-784d54a.ngbuilds.io/guide/user-input#binding-to-user-input-events instead?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
using the
ngModeldirective
This makes it sound as if two-way data binding is using (or depends on) ngModel, which is not true. Two-way data binding has nothing to do with ngModel, except for the fact that two-way data binding is often used to bind to ngModel.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
done
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Might also be worth mentioning (or showing in the example code-snippet above) that pipes can also take arguments.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Can you provide an example?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
https://angular.io/api/common/DatePipe#examples
(I.e. {{ interpolated_value | pipe_name : arg1 : arg2 }})
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can preview 96e6f45 at https://pr21569-96e6f45.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
96e6f45 to
ac2f558
Compare
|
You can preview ac2f558 at https://pr21569-ac2f558.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
You can preview 503647f at https://pr21569-503647f.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
A couple of minor comments.
Also the commits should be squashed together.
LGTM otherwise.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
503647f to
591b9a7
Compare
|
You can preview 591b9a7 at https://pr21569-591b9a7.ngbuilds.io/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Okay..finally passing all checks. Don't touch anything. :-) Merge merge quick. :-) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.