public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: Fixed lazy numbering in all documentation files (#27975)

Browse Source
This commit is contained in:
DECarreras
2020-10-01 09:45:05 -07:00
committed by GitHub
parent c3f277a6fe
commit 54df058b95
33 changed files with 158 additions and 158 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/developers/plugins/legacy/_index.md
+4 -4
View File
@@ -15,8 +15,8 @@ Grafana already has a strong community of contributors and plugin developers. By
## Short version
1. [Set up Grafana](https://github.com/grafana/grafana/blob/master/contribute/developer-guide.md)
2. Clone an example plugin into `/var/lib/grafana/plugins` or `data/plugins` (relative to grafana git repo if you're running development version from source dir)
3. Use one of our example plugins as a starting point
1. Clone an example plugin into `/var/lib/grafana/plugins` or `data/plugins` (relative to grafana git repo if you're running development version from source dir)
1. Use one of our example plugins as a starting point
Example plugins
@@ -87,8 +87,8 @@ export { WorldmapCtrl as PanelCtrl };
There are three ways that you can start developing a Grafana plugin.
1. Set up a Grafana development environment. [(described here)](https://github.com/grafana/grafana/blob/master/contribute/developer-guide.md) and place your plugin in the `data/plugins` folder.
2. Install Grafana and place your plugin in the plugins directory which is set in your [config file](/administration/configuration). By default this is `/var/lib/grafana/plugins` on Linux systems.
3. Place your plugin directory anywhere you like and specify it grafana.ini.
1. Install Grafana and place your plugin in the plugins directory which is set in your [config file](/administration/configuration). By default this is `/var/lib/grafana/plugins` on Linux systems.
1. Place your plugin directory anywhere you like and specify it grafana.ini.
We encourage people to set up the full Grafana environment so that you can get inspiration from the rest of the Grafana code base.
docs/sources/developers/plugins/legacy/style-guide.md
+4 -4
View File
@@ -146,8 +146,8 @@ We recommend that you use a linter for your JavaScript. For ES6, the standard li
### ES6 features
1. Use `const` if a variable is not going to be reassigned.
2. Prefer to use `let` instead `var` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-var-to-letconst))
3. Use arrow functions, which don’t shadow `this` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-function-expressions-to-arrow-functions)):
1. Prefer to use `let` instead `var` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-var-to-letconst))
1. Use arrow functions, which don’t shadow `this` ([Exploring ES6](http://exploringjs.com/es6/ch_core-features.html#_from-function-expressions-to-arrow-functions)):
```js
testDatasource() {
@@ -170,7 +170,7 @@ We recommend that you use a linter for your JavaScript. For ES6, the standard li
}
```
4. Use native _Promise_ object:
1. Use native _Promise_ object:
```js
metricFindQuery(query) {
@@ -190,4 +190,4 @@ We recommend that you use a linter for your JavaScript. For ES6, the standard li
}
```
5. If using Lodash, then be consistent and prefer that to the native ES6 array functions.
1. If using Lodash, then be consistent and prefer that to the native ES6 array functions.