electron/docs/development/coding-style.md

48 строки
2.1 KiB
Markdown
Исходник Обычный вид История

2015-08-31 08:31:14 +03:00
# Coding Style
These are the style guidelines for coding in Electron.
2013-09-09 11:35:57 +04:00
2016-03-08 00:58:49 +03:00
You can run `npm run lint` to show any style issues detected by `cpplint` and
`eslint`.
2016-03-07 20:46:05 +03:00
2013-08-15 02:43:35 +04:00
## C++ and Python
2015-08-31 08:31:14 +03:00
For C++ and Python, we follow Chromium's [Coding
Style](http://www.chromium.org/developers/coding-style). There is also a
script `script/cpplint.py` to check whether all files conform.
2013-08-15 02:43:35 +04:00
2015-08-31 08:31:14 +03:00
The Python version we are using now is Python 2.7.
2013-08-15 02:43:35 +04:00
2015-08-31 08:31:14 +03:00
The C++ code uses a lot of Chromium's abstractions and types, so it's
recommended to get acquainted with them. A good place to start is
Chromium's [Important Abstractions and Data Structures](https://www.chromium.org/developers/coding-style/important-abstractions-and-data-structures)
document. The document mentions some special types, scoped types (that
automatically release their memory when going out of scope), logging mechanisms
etc.
2016-03-07 20:43:04 +03:00
## JavaScript
2013-08-15 02:43:35 +04:00
2016-03-24 22:59:26 +03:00
* Write [standard](http://npm.im/standard) JavaScript style.
* Files should **NOT** end with new line, because we want to match Google's
styles.
* File names should be concatenated with `-` instead of `_`, e.g.
2016-03-07 20:43:04 +03:00
`file-name.js` rather than `file_name.js`, because in
[github/atom](https://github.com/github/atom) module names are usually in
2016-03-07 20:43:04 +03:00
the `module-name` form. This rule only applies to `.js` files.
* Use newer ES6/ES2015 syntax where appropriate
* [`const`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const)
for requires and other constants
* [`let`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let)
for defining variables
* [Arrow functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions)
instead of `function () { }`
* [Template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals)
instead of string concatenation using `+`
2013-08-15 02:43:35 +04:00
## API Names
When creating a new API, we should prefer getters and setters instead of
2015-08-31 08:31:14 +03:00
jQuery's one-function style. For example, `.getText()` and `.setText(text)`
are preferred to `.text([text])`. There is a
2015-08-31 08:31:14 +03:00
[discussion](https://github.com/atom/electron/issues/46) on this.