You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -185,7 +185,7 @@ To run the functional UI tests use the following commands
185
185
186
186
#### Running tests locally with your existing (and already running) ElasticSearch, Kibana, and Selenium Server:
187
187
188
-
Set your es and kibana ports in `test/intern.js` to 9220 and 5620, respecitively. You can configure your Selenium server to run the tests on Chrome,IE, or other browsers here.
188
+
Set your es and kibana ports in `test/intern.js` to 9220 and 5620, respectively. You can configure your Selenium server to run the tests on Chrome,IE, or other browsers here.
189
189
190
190
Once you've got the services running, execute the following:
191
191
@@ -196,7 +196,7 @@ npm run test:ui:runner
196
196
#### General notes:
197
197
198
198
- Using Page Objects pattern (https://theintern.github.io/intern/#writing-functional-test)
199
-
- At least the initial tests for the Settings, Discover, and Visualize tabs all depend on a very specific set of logstash-type data (generated with makelogs). Since that is a static set of data, all the Discover and Visualize tests use a specific Absolute time range. This gaurantees the same results each run.
199
+
- At least the initial tests for the Settings, Discover, and Visualize tabs all depend on a very specific set of logstash-type data (generated with makelogs). Since that is a static set of data, all the Discover and Visualize tests use a specific Absolute time range. This guarantees the same results each run.
200
200
- These tests have been developed and tested with Chrome and Firefox browser. In theory, they should work on all browsers (that's the benefit of Intern using Leadfoot).
201
201
- These tests should also work with an external testing service like https://saucelabs.com/ or https://www.browserstack.com/ but that has not been tested.
Copy file name to clipboardexpand all lines: STYLEGUIDE.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -586,7 +586,7 @@ Use slashes for both single line and multi line comments. Try to write
586
586
comments that explain higher level mechanisms or clarify difficult
587
587
segments of your code. **Don't use comments to restate trivial things**.
588
588
589
-
***Exception:*** Comment blocks describing a function and it's arguments (docblock) should start with `/**`, contain a single `*` at the begining of each line, and end with `*/`.
589
+
***Exception:*** Comment blocks describing a function and its arguments (docblock) should start with `/**`, contain a single `*` at the beginning of each line, and end with `*/`.
590
590
591
591
*Right:*
592
592
@@ -656,7 +656,7 @@ function ClassName() {
656
656
varClassName=function () {};
657
657
```
658
658
659
-
### Inhertiance should be done with a utility
659
+
### Inheritance should be done with a utility
660
660
661
661
While you can do it with pure JS, a utility will remove a lot of boilerplate, and be more readable and functional.
It is often the case that there are properties that can't be defined on the prototype, or work that needs to be done to completely create an object (like call it's Super class). This is all that should be done within constructors.
688
+
It is often the case that there are properties that can't be defined on the prototype, or work that needs to be done to completely create an object (like call its Super class). This is all that should be done within constructors.
689
689
690
690
Try to follow the [Write small functions](#write-small-functions) rule here too.
691
691
@@ -775,7 +775,7 @@ Several already exist, and can be found in `src/kibana/utils/_mixins.js`
775
775
776
776
## Filenames
777
777
778
-
All filenames should use `snake_case` and *can* start with an underscore if the module is not intended to be used outside of it's containing module.
778
+
All filenames should use `snake_case` and *can* start with an underscore if the module is not intended to be used outside of its containing module.
Angular routes are defined using a custom require modules named `routes` that remove much of the required boilerplate.
861
+
Angular routes are defined using a custom require module named `routes` that remove much of the required boilerplate.
862
862
863
863
```js
864
864
require('ui/routes')
@@ -871,7 +871,7 @@ require('ui/routes')
871
871
872
872
## Multiple attribute values
873
873
874
-
When a node has multiple attributes that would cause it to exceed the line character limit, each attribute including the first should be on its own line with a single indent. Also, when a node that is styled in this way has child nodes, there should be a blank line between the openening parent tag and the first child tag.
874
+
When a node has multiple attributes that would cause it to exceed the line character limit, each attribute including the first should be on its own line with a single indent. Also, when a node that is styled in this way has child nodes, there should be a blank line between the opening parent tag and the first child tag.
0 commit comments