jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

remove cut

Browse source
This commit is contained in:
Ilya Kantor 2018-02-06 13:07:22 +03:00
parent 37f1936622
commit be007e78ef
99 changed files with 0 additions and 198 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/03-code-quality/01-debugging-chrome/article.md
View file

@ -6,8 +6,6 @@ All modern browsers and most other environments support "debugging" -- a special
We'll be using Chrome here, because it's probably the most feature-rich in this aspect.
[cut]
## The "sources" pane
Your Chrome version may look a little bit different, but it still should be obvious what's there.

2
1-js/03-code-quality/02-coding-style/article.md
View file

@ -6,8 +6,6 @@ That is actually an art of programming -- to take a complex task and code it in
One thing to help is the good code style.
[cut]
## Syntax
A cheatsheet with the rules (more details below):

2
1-js/03-code-quality/04-ninja-code/article.md
View file

@ -13,8 +13,6 @@ Novice developers sometimes use them even better than programmer ninjas.
Read them carefully and find out who you are -- a ninja, a novice, or maybe a code reviewer?
[cut]
```warn header="Irony detected"
Many try to follow ninja paths. Few succeed.

2
1-js/03-code-quality/05-testing-mocha/article.md
View file

@ -4,8 +4,6 @@ Automated testing will be used in further tasks.
It's actually a part of the "educational minimum" of a developer.
[cut]
## Why we need tests?
When we write a function, we can usually imagine what it should do: which parameters give which results.