@@ -108,9 +108,9 @@ pnpm run lint
108
108
109
109
Diagnostic tool that checks for the following:
110
110
111
- - Unused CSS
112
- - Svelte A11y hints
113
- - TypeScript compiler errors
111
+ - Unused CSS
112
+ - Svelte A11y hints
113
+ - TypeScript compiler errors
114
114
115
115
``` bash
116
116
pnpm run check
@@ -130,11 +130,11 @@ doc-548-submit-a-pull-request-section-to-contribution-guide
130
130
131
131
When ` TYPE ` can be:
132
132
133
- - ** feat** - is a new feature
134
- - ** doc** - documentation only changes
135
- - ** cicd** - changes related to CI/CD system
136
- - ** fix** - a bug fix
137
- - ** refactor** - code change that neither fixes a bug nor adds a feature
133
+ - ** feat** - is a new feature
134
+ - ** doc** - documentation only changes
135
+ - ** cicd** - changes related to CI/CD system
136
+ - ** fix** - a bug fix
137
+ - ** refactor** - code change that neither fixes a bug nor adds a feature
138
138
139
139
** All PRs must include a commit message with a description of the changes made!**
140
140
@@ -175,22 +175,22 @@ $ git push origin [name_of_your_new_branch]
175
175
176
176
Before committing always make sure to run all available tools to improve the codebase:
177
177
178
- - Formatter
179
- - ` pnpm run format `
180
- - Tests
181
- - ` pnpm test `
182
- - Diagnostics
183
- - ` pnpm run check `
178
+ - Formatter
179
+ - ` pnpm run format `
180
+ - Tests
181
+ - ` pnpm test `
182
+ - Diagnostics
183
+ - ` pnpm run check `
184
184
185
185
### Performance
186
186
187
187
Page load times are a key consideration for users of all browsers and device types.
188
188
189
189
There are some general things we can do in front-end development:
190
190
191
- - Minimize HTTP requests
192
- - Minimize blocking – content should be readable before client-side processing
193
- - Lazy load "supplementary" content, especially images
191
+ - Minimize HTTP requests
192
+ - Minimize blocking – content should be readable before client-side processing
193
+ - Lazy load "supplementary" content, especially images
194
194
195
195
### Don't Repeat Yourself (DRY)
196
196
@@ -202,12 +202,12 @@ If you stick to this principle, you will ensure that you will only ever need to
202
202
203
203
Separate _ structure_ from _ presentation_ from _ behavior_ to aid maintainability and understanding.
204
204
205
- - Keep CSS (presentation), JS (behavior) and HTML (structure) in the same respective Svelte component
206
- - Avoid writing inline CSS or Javascript in HTML
207
- - Avoid writing CSS or HTML in Javascript
208
- - Don't choose HTML elements to imply style
209
- - Where appropriate, use CSS or Svelte rather than Javascript for animations and transitions
210
- - Try to use templates when defining markup in Javascript
205
+ - Keep CSS (presentation), JS (behavior) and HTML (structure) in the same respective Svelte component
206
+ - Avoid writing inline CSS or Javascript in HTML
207
+ - Avoid writing CSS or HTML in Javascript
208
+ - Don't choose HTML elements to imply style
209
+ - Where appropriate, use CSS or Svelte rather than Javascript for animations and transitions
210
+ - Try to use templates when defining markup in Javascript
211
211
212
212
### Write code to be read
213
213
0 commit comments