Hello, my friends, welcome to a brand new lesson, the last time we created our first project, but
we didn't really talk about any detail.
So let's get into it.
We'll talk about the angular project structure.
And if you look at the code, Ed will see the modules that were created when we built our first project.
So these are all the files and folders that anger Seelie created for us.
When we created that first project by default, so it can seem a little daunting at first glance, but
most of these are used for configuration and we don't really need to even, you know, worry about it.
We don't make any changes here.
I just want to show you these because.
Well.
Here they are, we'll talk about and learn some of the details throughout the entire course, but right
now we're just going to talk about what is necessary for us, OK?
So now we see the end to end test or Itogi folder, and that is first.
Unit tests and other tests, configuration section, so it's not going to make any changes in this section
for now so we can ignore it.
Yes, our C folder with our codes now, this is important.
So when we open the package that Jason file under this folder.
We see that all the dependencies over project are here.
And these dependencies are third party packages required for the correct operation of our project.
And it's also the place where all the dependencies in the package that Jason file are loaded and node
modules.
Now, here, have a look at something else, because also in this folder, there are all the packages
that we installed with Noad.
All the source codes that will be important to us.
Are in this SIRC or source, all of the apps, component services or e-mail files will use while developing
projects are all in this folder.
Also under this folder will see the app folder.
So, in fact, this folder contains an app module and component.
Now, angular applications have a modular structure and we can develop our applications with components
under modules.
So since the applications are developed modularly, it's easier to intervene as we develop our projects,
we don't have any difficulties even if we want to make changes in the early stages.
So app modules actually consist of structures such as core module for module and browser module.
And we can create some components under it as well, for example, the NAV bar, a component app component
or course component.
And since there are different components in the app module.
It's necessary to know which component will be run first when the application is running.
So we can specify this in the index e-mail file.
For example, we call the app component on the index page, and since this component is related to others,
the other components are also operated sequentially.
So we can call the other components that will run in the app component.
So you know what, let's go through the codes a little bit.
We talked about the Amadeu.
And we can see this module with the extension, T.S..
So it's written in, typescript.
In fact, these files are run by converting JavaScript.
We'll talk about that a little bit later and much more detail, so you don't really have to think about
it for now.
But we'll open this now.
Look at this so we can see the browser module and the core module that we mentioned.
And we can define the modules that we will use from outside within the imports.
So if we use a different module, we'd have to define it here as well.
For example, if we use a four module, we can define it and import it.
And here we see a map component and bootstrap.
So in other words, we define the component that will be called first when the application runs.
And when we look at them all here, all of them are already AB components.
And we see the JavaScript file, HTML file and access file.
So as you can see, the module contains components within it.
So I think it's pretty safe to say that the most important folder for us is SIRC.
And we had a look at the structure.
All right, so that's it for this lesson, we briefly talked about the angular folder structure, it
might seem a little packed and a little daunting at first glance, but we're going to get into it in
later lesson.
So for now, I think that's enough.
The more you use the folders, the better you're going to understand them.
All right.
So I want to see in the next lesson, though.
See you then.