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: README.md
+5-13Lines changed: 5 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,12 +9,9 @@ Copy the example files into the correct place:
9
9
10
10
```
11
11
cp .env.example .env
12
-
13
-
cp .env.webcomponent.example .env.webcomponent
14
12
```
15
13
16
-
Variables for the web application need to go into the `.env` file.
17
-
Variables for the web component can be placed in `.env.webcomponent`.
14
+
Variables for the web component can be placed in `.env`.
18
15
19
16
## Private repo setup (.npmrc)
20
17
@@ -32,7 +29,7 @@ In the project directory, you can run:
32
29
### `yarn start`
33
30
34
31
Runs the app in the development mode.\
35
-
Open [http://localhost:3010](http://localhost:3010) to view it in the browser.
32
+
Open [http://localhost:3011](http://localhost:3011) to view it in the browser.
36
33
37
34
The page will reload if you make edits.\
38
35
You will also see any lint errors in the console.
@@ -57,8 +54,9 @@ See the section about [deployment](https://facebook.github.io/create-react-app/d
57
54
Automated unit tests can be run via the `yarn test` command. These unit tests are written using the JavaScript testing framework `Jest` and make use of the tools provided by the [React Testing Library](https://testing-library.com/docs/). Automated accessibility testing for components is available via the `jest-axe` library. This can be achieved using the `haveNoViolations` matcher provided by `jest-axe`, although this does not guarantee that the tested components have no accessibility issues.
58
55
59
56
Integration testing is carried out via `cypress` and can be run using:
60
-
*`yarn exec cypress run` to run in the CLI
61
-
*`yarn exec cypress open` to run in the GUI
57
+
58
+
-`yarn exec cypress run` to run in the CLI
59
+
-`yarn exec cypress open` to run in the GUI
62
60
63
61
Currently, there are basic `cypress` tests for the standalone editor site, the web component and Mission Zero-related functionality. These can be found in the `cypress/e2e` directory. Screenshots and videos related to the most recent `cypress` test run can be found in `cypress/screenshots` and `cypress/videos` respectively.
64
62
@@ -80,12 +78,6 @@ The web component can be included in a page by using the `<editor-wc>` HTML elem
80
78
-`embedded`: Enable embedded mode which hides some functionality (defaults to `false`)
81
79
-`output_split_view`: Start with split view in output panel (defaults to `false`, i.e. tabbed view)
82
80
83
-
### `yarn start:wc`
84
-
85
-
Runs the web component in development mode. Open [http://localhost:3011](http://localhost:3011) to view it in the browser.
86
-
87
-
**NB** You need to have the main `yarn start` process running too.
88
-
89
81
It is possible to add query strings to control how the web component is configured. Any HTML attribute can be set on the query string, including `class`, `style` etc.
90
82
91
83
For example, to load the page with the Sense Hat always showing, add [`?sense_hat_always_enabled` to the URL](http://localhost:3011?sense_hat_always_enabled)
0 commit comments