Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,120 --> 00:00:05,740
In this lecture, we are going to review the files generated by the Create View Package.
2
00:00:05,760 --> 00:00:11,700
Most of the files should be familiar to us since we selected a few tools during installation.
3
00:00:11,700 --> 00:00:14,270
There will be new files in our project.
4
00:00:14,280 --> 00:00:17,460
Let's focus on the new files first.
5
00:00:17,460 --> 00:00:20,760
We're going to focus on the files in the root directory.
6
00:00:20,760 --> 00:00:25,980
The first file is called S lint RC dot CSJ.
7
00:00:26,010 --> 00:00:30,060
This file contains the configuration settings for S lint.
8
00:00:30,090 --> 00:00:34,380
Inside the exported object, there are a few settings being added.
9
00:00:34,380 --> 00:00:36,900
The first setting is called root.
10
00:00:36,930 --> 00:00:41,430
It's completely acceptable for subdirectories to have different rules.
11
00:00:41,430 --> 00:00:45,390
You can create a configuration file from within a directory.
12
00:00:45,420 --> 00:00:52,530
S lint will apply the rules from the inner directory instead of the configuration file in the root directory,
13
00:00:52,530 --> 00:00:58,170
we can specify a root configuration file by setting this property to true.
14
00:00:58,320 --> 00:01:02,250
Up next, we have an array called extends.
15
00:01:03,090 --> 00:01:06,730
Configuring the rules for Linux can be tedious.
16
00:01:06,750 --> 00:01:08,580
There are dozens of rules.
17
00:01:08,610 --> 00:01:11,000
Our file would become very large.
18
00:01:11,010 --> 00:01:16,480
To avoid large files, we can apply rules from other configuration files.
19
00:01:16,500 --> 00:01:20,680
In this array, we are applying rules from three files.
20
00:01:20,700 --> 00:01:23,850
The first file is called View Essential.
21
00:01:23,880 --> 00:01:27,960
There are rules for checking the code quality of view components.
22
00:01:27,990 --> 00:01:32,040
Next, there's the S lynch recommended rules.
23
00:01:32,070 --> 00:01:36,460
These rules are the recommended rules from the s lynch package.
24
00:01:36,480 --> 00:01:41,220
Lastly, there's the prettier rules as we discussed before.
25
00:01:41,250 --> 00:01:44,820
Prettier may conflict with the rules from s lynch.
26
00:01:44,850 --> 00:01:50,670
To avoid conflicts, this file configures s lynch not to clash with prettier.
27
00:01:50,790 --> 00:01:56,110
For most projects, the configuration settings from these files will be more than suitable.
28
00:01:56,130 --> 00:01:58,600
Let's move on to the last property.
29
00:01:58,620 --> 00:02:00,460
It's called overrides.
30
00:02:00,480 --> 00:02:05,150
Sometimes we may not want to apply the same rules to all files.
31
00:02:05,160 --> 00:02:10,009
We can use special rules for specific files by adding this array.
32
00:02:10,020 --> 00:02:14,250
In this array, each object can represent a set of files.
33
00:02:14,250 --> 00:02:20,310
In this example, a special set of rules are being applied to Cypress Test files.
34
00:02:20,460 --> 00:02:26,910
Overall, that does it for the Lynch configuration file before moving on to the next file.
35
00:02:26,940 --> 00:02:31,770
Check out the resource section of this lecture for a link to a style guide.
36
00:02:34,000 --> 00:02:38,960
The Style Guide lists recommended guidelines for formatting and writing code.
37
00:02:38,980 --> 00:02:42,170
I want to emphasize the word recommended.
38
00:02:42,190 --> 00:02:44,740
Most of these guidelines are optional.
39
00:02:44,770 --> 00:02:47,780
Vue has four categories of rules.
40
00:02:47,800 --> 00:02:55,300
They are the essential, strongly recommended, recommended and use with caution categories.
41
00:02:55,330 --> 00:02:59,460
Rules in the essential category are considered highly important.
42
00:02:59,470 --> 00:03:01,350
We must follow these rules.
43
00:03:01,360 --> 00:03:04,830
Otherwise we may encounter errors in our application.
44
00:03:04,840 --> 00:03:07,300
You should always follow them as they are considered.
45
00:03:07,300 --> 00:03:08,670
Standard Practice.
46
00:03:08,680 --> 00:03:11,890
The other categories contain optional rules.
47
00:03:11,890 --> 00:03:19,210
The last category is called use with caution, the rules in the use with caution category or rules that
48
00:03:19,210 --> 00:03:21,310
are for special edge cases.
49
00:03:21,310 --> 00:03:24,850
They're not something you should regularly use unless you need to.
50
00:03:24,880 --> 00:03:30,560
Throughout this course, I'm going to try my best to follow the rules specified by you.
51
00:03:30,580 --> 00:03:35,710
At times, I may deviate from these rules to better explain concepts.
52
00:03:35,710 --> 00:03:40,780
One example is that it's recommended not to perform log statements in our code.
53
00:03:40,780 --> 00:03:45,460
However, we may need to log values for debugging purposes.
54
00:03:45,460 --> 00:03:49,000
Feel free to adhere to these rules as you wish.
55
00:03:49,030 --> 00:03:53,080
Is, lint has been configured to follow most of these rules.
56
00:03:53,140 --> 00:03:54,690
Head back to the editor.
57
00:03:54,700 --> 00:03:56,790
Let's move on to the next file.
58
00:03:56,800 --> 00:04:03,570
The Cypress dot config dot js file contains the settings for the cypress tool.
59
00:04:03,580 --> 00:04:07,550
Cypress is a tool for performing testing on an application.
60
00:04:07,570 --> 00:04:10,360
Testing is a topic covered in this course.
61
00:04:10,360 --> 00:04:14,820
For now, we're going to ignore this file until we talk about testing.
62
00:04:14,830 --> 00:04:16,899
There may be errors in this file.
63
00:04:16,899 --> 00:04:18,670
You can safely ignore them.
64
00:04:18,670 --> 00:04:21,070
They will not impact our application.
65
00:04:21,100 --> 00:04:24,220
Moving on, let's check out the package file.
66
00:04:24,220 --> 00:04:28,900
Inside this file, we're going to find an extensive list of dependencies.
67
00:04:28,900 --> 00:04:32,110
We'll explore them as we progress through the course.
68
00:04:32,110 --> 00:04:35,860
Let's shift our focus to the scripts object.
69
00:04:35,890 --> 00:04:38,920
We don't have the usual list of commands.
70
00:04:38,920 --> 00:04:43,360
The Create View package will supply us with additional commands.
71
00:04:43,360 --> 00:04:46,060
Three commands are related to tests.
72
00:04:46,060 --> 00:04:50,320
Once again, these commands will be reviewed during the testing section.
73
00:04:50,320 --> 00:04:53,380
Of this course, you can safely ignore them.
74
00:04:53,380 --> 00:04:57,790
The last command is for landing our project in an upcoming lecture.
75
00:04:57,790 --> 00:04:59,830
We are going to automate lynching.
76
00:04:59,830 --> 00:05:04,690
It'll be easier to automate this process as opposed to running a command.
77
00:05:04,810 --> 00:05:08,710
Overall, these are the major changes in the root directory.
78
00:05:08,710 --> 00:05:11,110
Let's start looking at the folders.
79
00:05:11,110 --> 00:05:14,080
The first folder is called VS Code.
80
00:05:14,080 --> 00:05:17,350
This directory may be available for some of you.
81
00:05:17,380 --> 00:05:22,060
If it is, this folder will contain settings for Visual Studio code.
82
00:05:22,090 --> 00:05:24,310
You may get warnings from the editor.
83
00:05:24,310 --> 00:05:29,860
If you don't want to constantly receive warnings, you can safely delete this directory.
84
00:05:29,860 --> 00:05:31,870
I'm going to quickly do so.
85
00:05:33,930 --> 00:05:37,250
The public directory is mostly the same as before.
86
00:05:37,260 --> 00:05:40,530
We have the five icon file, nothing else to it.
87
00:05:40,560 --> 00:05:45,450
The most significant change is in the source directory, unlike before.
88
00:05:45,480 --> 00:05:50,290
Three directories have been created called views, stores and router.
89
00:05:50,310 --> 00:05:53,790
We'll be exploring these directories throughout the project.
90
00:05:53,820 --> 00:05:55,170
Don't worry about them.
91
00:05:55,170 --> 00:06:00,210
We'll soon become comfortable with everything within the components directory.
92
00:06:00,240 --> 00:06:03,720
A new directory was created called tests.
93
00:06:06,100 --> 00:06:08,620
It's another directory for writing tests.
94
00:06:08,650 --> 00:06:14,920
Tests are a topic we'll cover in a separate section that sums up everything in the next lecture.
95
00:06:14,920 --> 00:06:18,880
Let's start configuring our editors to format our code.
8957
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.