In this lecture, we're going to review the last few files in the source directory.
We've gone over the most critical topics in this section.
The rest of the files will either be revisited or briefly discussed in this lecture.
Let's begin in the source directory, we have a folder called assets.
The assets folder can store static asset files.
As we discussed before, the angular Seelye will process the files in our project.
However, there's one exception to this rule.
The files stored in the assets directory will be copied over to the final build during compilation.
This directory is perfect for storing images, fonts or any other static file you want to be included
in your project.
It's not a victory for storing CSX.
Instead, we should store CSX in a components respective style sheet file.
Next, we have a file called Poly Dot and us.
The Poly Scott T.S. File contains code for supporting features that aren't available in the browser.
Not all browsers are considered equal.
Some browsers don't support every feature we need for our app to work.
The Polly Fills file will check if the current browser supports the features it needs if it doesn't.
The feature will be recreated this way.
Our app will work on any browser, especially the older ones.
The following file in the list is the Styles Access file.
Initially, this file will be empty.
It's where we can end global styles to our app.
Normally you should add CSIS to a component.
However, if you need to apply styles on a global level, you should add them here.
Up next, we have the tests file.
This file will contain the configuration settings for running tests.
Testing is not a topic we'll be exploring in this course.
You can safely ignore this file.
It will not impact the behavior of our app since we're on the topic of tests.
Another test file in the app directory is called App Dock Component Aspects Angular will generate test
files for your components.
Test files how the spec extension, which is short for spec. It's common to have this extension in the
name.
It's not required, but recommended.
One last thing Let's open the app module acts file.
This file is almost an exact copy of the original module file.
It's missing a property called providers.
I decided not to include this property because we would need to discuss what services are.
It's not required to have this property in a module unless we're using services.
It's a topic we will be exploring in a future section.
I just wanted to mention it for those of you who caught this.
With that being said, we're finished reviewing the default project.
There's so much going on under the hood by running the engine new command Angular generated this entire
project.
Thus, we have the bare minimum for starting and angular projects in the next section.
We're going to spend some time on components.
Writing components is mostly what you're going to be doing during the development of an angular app.
Apps are mostly built with components.
When you're ready, I'll see you in the next section.