@royaloperahouse/chord 1.11.0-e-chord-development → 1.12.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +5 -34
- package/README.GIT +275 -0
- package/README.md +40 -248
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,50 +1,21 @@
|
|
|
1
|
-
|
|
1
|
+
## [1.12.0]
|
|
2
|
+
- Search: Extend ContentSummary and SearchBar components to support new search results
|
|
2
3
|
|
|
3
|
-
## [1.11.0
|
|
4
|
-
-
|
|
5
|
-
|
|
6
|
-
## [1.10.0-a]
|
|
7
|
-
- ContentSummary: make image clickable
|
|
4
|
+
## [1.11.0]
|
|
5
|
+
- Carousels: Rewrite logic that cuts description, to support older browsers
|
|
8
6
|
|
|
9
7
|
## [1.10.0]
|
|
10
8
|
- PageHeadingImpact: Replace CSS background-image with HTML image element
|
|
11
|
-
## [1.9.0]
|
|
12
|
-
- Card: Add a new prop for the hover line color
|
|
13
|
-
## [1.9.0-c]
|
|
14
|
-
- ContentSummary: make image clickable
|
|
15
|
-
|
|
16
|
-
## [1.9.0-b]
|
|
17
|
-
- ContentSummary: change image size
|
|
18
|
-
- SearchBar: Export component
|
|
19
|
-
|
|
20
|
-
## [1.9.0-a]
|
|
21
|
-
- ContentSummary: change image props
|
|
22
9
|
|
|
23
10
|
## [1.9.0]
|
|
24
11
|
- Card: Add a new prop for the hover line color
|
|
25
12
|
|
|
26
|
-
## [1.8.1-h]
|
|
27
|
-
- ContentSummary: add exports
|
|
28
|
-
|
|
29
|
-
## [1.8.1-g]
|
|
30
|
-
- ContentSummary: refactor
|
|
31
|
-
|
|
32
|
-
## [1.8.1-f]
|
|
33
|
-
- ContentSummary: update conditional rendering
|
|
34
|
-
|
|
35
|
-
## [1.8.1-c]
|
|
36
|
-
- ContentSummary: update for Search results
|
|
37
|
-
- ContentSummarySection: remove
|
|
38
|
-
|
|
39
|
-
## [1.8.1-b]
|
|
40
|
-
- Card: add new prop for the line color on hover
|
|
41
|
-
|
|
42
13
|
## [1.8.0]
|
|
43
14
|
- SearchBar: Disable
|
|
44
15
|
|
|
45
16
|
## [1.7.2]
|
|
46
17
|
- Add imageAltText to Card component
|
|
47
|
-
|
|
18
|
+
|
|
48
19
|
## [1.7.0]
|
|
49
20
|
- Add new ContentSummary component
|
|
50
21
|
- Add new ContentSummarySection component
|
package/README.GIT
ADDED
|
@@ -0,0 +1,275 @@
|
|
|
1
|
+
# Royal Opera House Chord - Front End Design System
|
|
2
|
+
|
|
3
|
+
Welcome to the Royal Opera House Front End Design System, `@royaloperahouse/chord`
|
|
4
|
+
|
|
5
|
+
This package is a library of UI components intended to be used in the ROH website.
|
|
6
|
+
|
|
7
|
+
It uses React, TypeScript, TSDX and Storybook.
|
|
8
|
+
|
|
9
|
+
The NPM packages are published at [https://www.npmjs.com/package/@royaloperahouse/chord](https://www.npmjs.com/package/@royaloperahouse/chord)
|
|
10
|
+
|
|
11
|
+
The Storybook for the latest version of the library is hosted at [chord.roh.org.uk](chord.roh.org.uk)
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
## Prerequisites
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
* Make sure the required package dependencies are installed using `yarn install`
|
|
18
|
+
|
|
19
|
+
* **To deploy the storybook publicly** you will need credentials for the **parent** 'Royal Opera House' AWS account in your `~/.aws/credentials` file.
|
|
20
|
+
* The deploy script expects these to be called `[parent]`.
|
|
21
|
+
|
|
22
|
+
* You can find these values at:
|
|
23
|
+
|
|
24
|
+
*AWS 'Your Applications' page -> 'Royal Opera House' -> 'Developer Access' -> 'Command line or programmatic access'*
|
|
25
|
+
|
|
26
|
+
* **To deploy a preview** for demo / QA you will need the `CHROMATIC_PROJECT_TOKEN` -- find this in 1Password
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
* **To publish the NPM package** you will need the ROH `NPM_TOKEN` -- find this in 1Password
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
## Versioning
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
We use [Semantic Versioning](https://semver.org/) for Chord.
|
|
36
|
+
|
|
37
|
+
Given a version number MAJOR.MINOR.PATCH, increment the:
|
|
38
|
+
|
|
39
|
+
* MAJOR version when you make incompatible library changes
|
|
40
|
+
* MINOR version when you add functionality in a backwards compatible manner
|
|
41
|
+
* PATCH version when you make backwards compatible bug fixes
|
|
42
|
+
|
|
43
|
+
When you create a new release always update the `CHANGELOG` and `package.json`
|
|
44
|
+
|
|
45
|
+
Increment your version from the latest stable version on `chord-releases`
|
|
46
|
+
|
|
47
|
+
|
|
48
|
+
## Deploying the Storybook
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
### **1. To build and deploy locally**
|
|
52
|
+
|
|
53
|
+
You can quickly build and serve the contents of `/storybook-static` from your local machine, for development and manual testing. To do this run:
|
|
54
|
+
|
|
55
|
+
```bash
|
|
56
|
+
yarn storybook
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
By default the storybook will be accessible at
|
|
60
|
+
[http://localhost:6006/]()
|
|
61
|
+
|
|
62
|
+
The server will hot-reload on most changes.
|
|
63
|
+
|
|
64
|
+
### **2. To deploy a preview version remotely**
|
|
65
|
+
|
|
66
|
+
You can deploy a release candidate, or work-in-progress to [Chromatic](https://www.chromatic.com/) for showcase or QA.
|
|
67
|
+
|
|
68
|
+
**NOTE:** you will need the `CHROMATIC_PROJECT_TOKEN` as described in *Prerequisites* above.
|
|
69
|
+
|
|
70
|
+
Either set the token as a shell variable or use a `.env` file in the chord root directory containing the token, as so:
|
|
71
|
+
|
|
72
|
+
```
|
|
73
|
+
CHROMATIC_PROJECT_TOKEN=tokengoeshere
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
Run:
|
|
77
|
+
|
|
78
|
+
```
|
|
79
|
+
yarn deploy-storybook-dev
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
to build and deploy the storybook from your repo to Chromatic.
|
|
83
|
+
|
|
84
|
+
You will find the address of your deployed storybook in the console output, looking something like this:
|
|
85
|
+
|
|
86
|
+
`→ View your Storybook at https://randomHexString-randomAlphabeticalString.chromatic.com`
|
|
87
|
+
|
|
88
|
+
### **3. To deploy a release version**
|
|
89
|
+
|
|
90
|
+
You can deploy the contents of `./storybook-static` to S3 as a static site, which is permanently accessible at [chord.roh.org.uk](chord.roh.org.uk)
|
|
91
|
+
|
|
92
|
+
**NOTE:** To do this you will need the correct `AWS` credentials set up, as described in *Prerequisites* above.
|
|
93
|
+
|
|
94
|
+
First build the storybook using:
|
|
95
|
+
|
|
96
|
+
```
|
|
97
|
+
yarn build-storybook
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
then run:
|
|
101
|
+
|
|
102
|
+
```bash
|
|
103
|
+
yarn deploy-storybook
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
> **IMPORTANT:** This URL is intended to showcase the latest stable version of Chord, it should be kept up to date with the main `chord-releases` branch and should **only** be used for release versions. If you want to deploy a development version follow the steps above under *To deploy a preview version remotely*.
|
|
107
|
+
|
|
108
|
+
|
|
109
|
+
## Releasing a New Package Version
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
This is the procedure for releasing a new Chord NPM package.
|
|
113
|
+
|
|
114
|
+
There are two types of package:
|
|
115
|
+
|
|
116
|
+
A **snapshot** can be published to use a development version of the Chord library in our frontend staging environments, to perform integrated, manual testing.
|
|
117
|
+
|
|
118
|
+
A **stable** package is published for use in production.
|
|
119
|
+
|
|
120
|
+
**NOTE:** You will need the `NPM_TOKEN`, as described in 'Prerequisites' above.
|
|
121
|
+
|
|
122
|
+
### **1. To release a snapshot version**
|
|
123
|
+
|
|
124
|
+
> **IMPORTANT:** Make sure you always publish your **snapshots** from `chord-development` after merging in your feature branch.
|
|
125
|
+
|
|
126
|
+
For snapshots, `RELEASE_VERSION` should be the same as the latest **stable** version of the Chord Library, as found in `chord-releases`, followed by an **unused** lowercase letter.
|
|
127
|
+
|
|
128
|
+
For example, if the latest stable release was 1.42.0, and the last snapshot published to NPM was 1.42.0-w, you would use RELEASE_VERSION `1.42.0-x`
|
|
129
|
+
|
|
130
|
+
To publish a snapshot use:
|
|
131
|
+
|
|
132
|
+
```bash
|
|
133
|
+
NPM_ROH_TOKEN={NPM_TOKEN} RELEASE_VERSION={RELEASE_VERSION} yarn publish-snapshot
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
The version published to NPM will be named, e.g. `1.42.0-a-chord-development`, use this to install the snapshot package in the frontend repos.
|
|
137
|
+
|
|
138
|
+
### **2. To release a stable version**
|
|
139
|
+
|
|
140
|
+
> **IMPORTANT:** Make sure you always publish your **stable** packages from `chord-releases` after merging in your feature branch.
|
|
141
|
+
|
|
142
|
+
For stable releases, increment your version from the latest **stable** version found on `chord-releases`, following the rules described in *Versioning* above, and use this as `RELEASE_VERSION`. (Make sure it matches the version in your `package.json` and `CHANGELOG.md`!)
|
|
143
|
+
|
|
144
|
+
To publish a stable package use:
|
|
145
|
+
|
|
146
|
+
```bash
|
|
147
|
+
NPM_ROH_TOKEN={NPM_TOKEN} RELEASE_VERSION={RELEASE_VERSION} yarn publish-release
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
|
|
151
|
+
## Using the Package
|
|
152
|
+
---
|
|
153
|
+
|
|
154
|
+
The package is deployed to NPM, and can be installed using yarn or npm:
|
|
155
|
+
|
|
156
|
+
```bash
|
|
157
|
+
npm i --save @royaloperahouse/chord
|
|
158
|
+
```
|
|
159
|
+
```bash
|
|
160
|
+
yarn add @royaloperahouse/chord
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
|
|
164
|
+
## Testing
|
|
165
|
+
---
|
|
166
|
+
|
|
167
|
+
To **Lint** the package use:
|
|
168
|
+
|
|
169
|
+
```bash
|
|
170
|
+
yarn lint
|
|
171
|
+
# Use the --fix option to perform automatic fixes
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
To run the **unit tests** (using Jest) use:
|
|
175
|
+
|
|
176
|
+
```bash
|
|
177
|
+
yarn test
|
|
178
|
+
|
|
179
|
+
# Use the -u option to update snapshots if needed
|
|
180
|
+
# Run `yarn test:watch` to re-run tests on changes
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
To **run and and store the unit tests** for display in storybook use:
|
|
184
|
+
|
|
185
|
+
```bash
|
|
186
|
+
yarn test-storybook
|
|
187
|
+
# Use the -u option to update snapshots if needed
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
|
|
191
|
+
## Development Process
|
|
192
|
+
---
|
|
193
|
+
|
|
194
|
+
### **1. Branching Model**
|
|
195
|
+
* The Chord project lives in the `roh-components` *monorepo*
|
|
196
|
+
* When working on Chord, treat the `roh-components/packages/chord` directory as your root
|
|
197
|
+
* The Chord **development** branch is currently `chord-development`
|
|
198
|
+
* The Chord **main** branch is currently `chord-releases`
|
|
199
|
+
* All work should be done on a correctly named **feature branch** of the format: `issueType/ticketNumber-short-description-of-feature`, e.g. `feature/RD-1234-update-chord-documentation`
|
|
200
|
+
* Always create your feature branch FROM, and submit pull requests TO, the **main** branch
|
|
201
|
+
* For **QA / UAT** of a Chord component in isolation: following review you should deploy a preview version to Chromatic straight from your **feature branch** _without_ merging to development
|
|
202
|
+
* For releasing an **NPM snapshot**: merge your feature branch into the **development** branch and publish the NPM snapshot from there
|
|
203
|
+
|
|
204
|
+
### **2. Detailed Workflow**
|
|
205
|
+
|
|
206
|
+
#### **Before review:**
|
|
207
|
+
|
|
208
|
+
* Git pull the latest version of `chord-releases`
|
|
209
|
+
* Checkout a new, correctly-named feature branch from `chord releases`
|
|
210
|
+
* Do your work on this feature branch
|
|
211
|
+
* Run: `yarn lint`
|
|
212
|
+
* Run: `yarn test`
|
|
213
|
+
* Commit your changes
|
|
214
|
+
* Create a pull request from your feature branch to `chord-releases`
|
|
215
|
+
* Add the appropriate reviewers
|
|
216
|
+
|
|
217
|
+
#### **Before QA / UAT:**
|
|
218
|
+
|
|
219
|
+
After your PR is approved, you have two options:
|
|
220
|
+
|
|
221
|
+
**i.** For QA of a component in isolation:
|
|
222
|
+
|
|
223
|
+
* Follow the steps above in *Deploying the Storybook -> 2. Deploying a preview version remotely*
|
|
224
|
+
* Share the generated Chromatic URL with the appropriate people for QA / UAT
|
|
225
|
+
|
|
226
|
+
**ii.** For integrated testing of a component in the frontend staging environments:
|
|
227
|
+
|
|
228
|
+
* Check out the `chord-development` branch
|
|
229
|
+
* Merge your work in to `chord-development`
|
|
230
|
+
* Follow the steps above under *Publishing a New Package Version -> 1. To release a snapshot version*
|
|
231
|
+
* Git push the updated `chord-development` branch to remote
|
|
232
|
+
* Finally, in the frontend repo:
|
|
233
|
+
|
|
234
|
+
1. Update the `package.json` to reference the new snapshot version
|
|
235
|
+
2. Run: `yarn install`
|
|
236
|
+
3. Deploy the frontend to a staging environment
|
|
237
|
+
|
|
238
|
+
#### **When ready for production:**
|
|
239
|
+
|
|
240
|
+
* Return to your chord **feature branch**
|
|
241
|
+
* Update the chord version in `package.json`, incrementing from the last **stable** release, found in `chord-releases`, and following the rules described in the *Versioning* section
|
|
242
|
+
* Update `CHANGELOG.md`, adding the new version number and a short description of your changes
|
|
243
|
+
* Run: `yarn lint`
|
|
244
|
+
* Run: `yarn test`
|
|
245
|
+
* Run: `yarn test-storybook -u`
|
|
246
|
+
* Run: `yarn build-storybook`
|
|
247
|
+
* Git commit, push, and update your PR for final approval
|
|
248
|
+
* Merge your approved PR to `chord-releases`
|
|
249
|
+
* Follow the steps in *Publishing a New Package Version -> 2. To release a stable version* to publish the NPM package
|
|
250
|
+
* Finally, follow the steps in *Deploying The Storybook -> 3. To deploy a release version*, to update the public Chord Storybook page
|
|
251
|
+
|
|
252
|
+
Once you have successfully published a new release version, you can open a ticket to update to this version in any of the frontend repos.
|
|
253
|
+
|
|
254
|
+
|
|
255
|
+
## Notes
|
|
256
|
+
---
|
|
257
|
+
### The `storybook-static` folder
|
|
258
|
+
|
|
259
|
+
This folder contains all the HTML / JS required to deploy the Storybook as a static site. It's autogenerated whenever the Storybook is built and therefore will show up a lot of merge conflicts when you merge other branches into your feature branch. It is best to leave generating the storybook until the later part of your workflow, but in case you run into conflicts earlier, it's ok to just delete the folder and regenerate using:
|
|
260
|
+
|
|
261
|
+
```bash
|
|
262
|
+
yarn build-storybook
|
|
263
|
+
```
|
|
264
|
+
|
|
265
|
+
For the same reason changes to this folder will cause a lot of big diffs, when looking at a PR, but can mostly be skimmed over unless something looks unusual.
|
|
266
|
+
|
|
267
|
+
---
|
|
268
|
+
### Examples
|
|
269
|
+
|
|
270
|
+
There is an example implementation in the example folder. Alternatively there are also integration examples in storybook. Make sure to keep these updated so as to showcase the current components available.
|
|
271
|
+
|
|
272
|
+
---
|
|
273
|
+
### Bundle analysis
|
|
274
|
+
|
|
275
|
+
Calculate the real cost of your library using [size-limit](https://github.com/ai/size-limit) with `yarn size` and visualize it with `yarn analyze`.
|
package/README.md
CHANGED
|
@@ -1,275 +1,67 @@
|
|
|
1
|
-
# Royal Opera House
|
|
1
|
+
# Royal Opera House - chord
|
|
2
2
|
|
|
3
|
-
Welcome to the Royal Opera House
|
|
3
|
+
Welcome to the Royal Opera House library components `@royaloperahouse/chord`.
|
|
4
4
|
|
|
5
5
|
This package is a library of UI components intended to be used in the ROH website.
|
|
6
6
|
|
|
7
|
-
It uses React, TypeScript, TSDX and Storybook.
|
|
8
7
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
The Storybook for the latest version of the library is hosted at [chord.roh.org.uk](chord.roh.org.uk)
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
## Prerequisites
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
* Make sure the required package dependencies are installed using `yarn install`
|
|
18
|
-
|
|
19
|
-
* **To deploy the storybook publicly** you will need credentials for the **parent** 'Royal Opera House' AWS account in your `~/.aws/credentials` file.
|
|
20
|
-
* The deploy script expects these to be called `[parent]`.
|
|
21
|
-
|
|
22
|
-
* You can find these values at:
|
|
23
|
-
|
|
24
|
-
*AWS 'Your Applications' page -> 'Royal Opera House' -> 'Developer Access' -> 'Command line or programmatic access'*
|
|
25
|
-
|
|
26
|
-
* **To deploy a preview** for demo / QA you will need the `CHROMATIC_PROJECT_TOKEN` -- find this in 1Password
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
* **To publish the NPM package** you will need the ROH `NPM_TOKEN` -- find this in 1Password
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
## Versioning
|
|
33
|
-
---
|
|
34
|
-
|
|
35
|
-
We use [Semantic Versioning](https://semver.org/) for Chord.
|
|
36
|
-
|
|
37
|
-
Given a version number MAJOR.MINOR.PATCH, increment the:
|
|
38
|
-
|
|
39
|
-
* MAJOR version when you make incompatible library changes
|
|
40
|
-
* MINOR version when you add functionality in a backwards compatible manner
|
|
41
|
-
* PATCH version when you make backwards compatible bug fixes
|
|
42
|
-
|
|
43
|
-
When you create a new release always update the `CHANGELOG` and `package.json`
|
|
44
|
-
|
|
45
|
-
Increment your version from the latest stable version on `chord-releases`
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
## Deploying the Storybook
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
### **1. To build and deploy locally**
|
|
52
|
-
|
|
53
|
-
You can quickly build and serve the contents of `/storybook-static` from your local machine, for development and manual testing. To do this run:
|
|
8
|
+
## Install
|
|
54
9
|
|
|
55
10
|
```bash
|
|
56
|
-
|
|
11
|
+
npm i --save @royaloperahouse/chord
|
|
57
12
|
```
|
|
58
|
-
|
|
59
|
-
By default the storybook will be accessible at
|
|
60
|
-
[http://localhost:6006/]()
|
|
61
|
-
|
|
62
|
-
The server will hot-reload on most changes.
|
|
63
|
-
|
|
64
|
-
### **2. To deploy a preview version remotely**
|
|
65
|
-
|
|
66
|
-
You can deploy a release candidate, or work-in-progress to [Chromatic](https://www.chromatic.com/) for showcase or QA.
|
|
67
|
-
|
|
68
|
-
**NOTE:** you will need the `CHROMATIC_PROJECT_TOKEN` as described in *Prerequisites* above.
|
|
69
|
-
|
|
70
|
-
Either set the token as a shell variable or use a `.env` file in the chord root directory containing the token, as so:
|
|
71
|
-
|
|
72
|
-
```
|
|
73
|
-
CHROMATIC_PROJECT_TOKEN=tokengoeshere
|
|
74
|
-
```
|
|
75
|
-
|
|
76
|
-
Run:
|
|
77
|
-
|
|
78
|
-
```
|
|
79
|
-
yarn deploy-storybook-dev
|
|
80
|
-
```
|
|
81
|
-
|
|
82
|
-
to build and deploy the storybook from your repo to Chromatic.
|
|
83
|
-
|
|
84
|
-
You will find the address of your deployed storybook in the console output, looking something like this:
|
|
85
|
-
|
|
86
|
-
`→ View your Storybook at https://randomHexString-randomAlphabeticalString.chromatic.com`
|
|
87
|
-
|
|
88
|
-
### **3. To deploy a release version**
|
|
89
|
-
|
|
90
|
-
You can deploy the contents of `./storybook-static` to S3 as a static site, which is permanently accessible at [chord.roh.org.uk](chord.roh.org.uk)
|
|
91
|
-
|
|
92
|
-
**NOTE:** To do this you will need the correct `AWS` credentials set up, as described in *Prerequisites* above.
|
|
93
|
-
|
|
94
|
-
First build the storybook using:
|
|
95
|
-
|
|
96
|
-
```
|
|
97
|
-
yarn build-storybook
|
|
98
|
-
```
|
|
99
|
-
|
|
100
|
-
then run:
|
|
101
|
-
|
|
102
13
|
```bash
|
|
103
|
-
yarn
|
|
14
|
+
yarn add @royaloperahouse/chord
|
|
104
15
|
```
|
|
105
16
|
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
## Releasing a New Package Version
|
|
110
|
-
---
|
|
111
|
-
|
|
112
|
-
This is the procedure for releasing a new Chord NPM package.
|
|
113
|
-
|
|
114
|
-
There are two types of package:
|
|
115
|
-
|
|
116
|
-
A **snapshot** can be published to use a development version of the Chord library in our frontend staging environments, to perform integrated, manual testing.
|
|
117
|
-
|
|
118
|
-
A **stable** package is published for use in production.
|
|
119
|
-
|
|
120
|
-
**NOTE:** You will need the `NPM_TOKEN`, as described in 'Prerequisites' above.
|
|
17
|
+
## Usage
|
|
121
18
|
|
|
122
|
-
|
|
19
|
+
```javascript
|
|
20
|
+
import {
|
|
21
|
+
Footer, GlobalStyles, ThemeProvider, ThemeType,
|
|
22
|
+
} from '@royaloperahouse/chord';
|
|
123
23
|
|
|
124
|
-
> **IMPORTANT:** Make sure you always publish your **snapshots** from `chord-development` after merging in your feature branch.
|
|
125
|
-
|
|
126
|
-
For snapshots, `RELEASE_VERSION` should be the same as the latest **stable** version of the Chord Library, as found in `chord-releases`, followed by an **unused** lowercase letter.
|
|
127
|
-
|
|
128
|
-
For example, if the latest stable release was 1.42.0, and the last snapshot published to NPM was 1.42.0-w, you would use RELEASE_VERSION `1.42.0-x`
|
|
129
|
-
|
|
130
|
-
To publish a snapshot use:
|
|
131
|
-
|
|
132
|
-
```bash
|
|
133
|
-
NPM_ROH_TOKEN={NPM_TOKEN} RELEASE_VERSION={RELEASE_VERSION} yarn publish-snapshot
|
|
134
|
-
```
|
|
135
|
-
|
|
136
|
-
The version published to NPM will be named, e.g. `1.42.0-a-chord-development`, use this to install the snapshot package in the frontend repos.
|
|
137
|
-
|
|
138
|
-
### **2. To release a stable version**
|
|
139
|
-
|
|
140
|
-
> **IMPORTANT:** Make sure you always publish your **stable** packages from `chord-releases` after merging in your feature branch.
|
|
141
|
-
|
|
142
|
-
For stable releases, increment your version from the latest **stable** version found on `chord-releases`, following the rules described in *Versioning* above, and use this as `RELEASE_VERSION`. (Make sure it matches the version in your `package.json` and `CHANGELOG.md`!)
|
|
143
|
-
|
|
144
|
-
To publish a stable package use:
|
|
145
|
-
|
|
146
|
-
```bash
|
|
147
|
-
NPM_ROH_TOKEN={NPM_TOKEN} RELEASE_VERSION={RELEASE_VERSION} yarn publish-release
|
|
148
|
-
```
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
## Using the Package
|
|
152
|
-
---
|
|
153
|
-
|
|
154
|
-
The package is deployed to NPM, and can be installed using yarn or npm:
|
|
155
|
-
|
|
156
|
-
```bash
|
|
157
|
-
npm i --save @royaloperahouse/chord
|
|
158
|
-
```
|
|
159
|
-
```bash
|
|
160
|
-
yarn add @royaloperahouse/chord
|
|
161
|
-
```
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
## Testing
|
|
165
|
-
---
|
|
166
|
-
|
|
167
|
-
To **Lint** the package use:
|
|
168
|
-
|
|
169
|
-
```bash
|
|
170
|
-
yarn lint
|
|
171
|
-
# Use the --fix option to perform automatic fixes
|
|
172
24
|
```
|
|
25
|
+
## Sample
|
|
173
26
|
|
|
174
|
-
|
|
27
|
+
```javascript
|
|
175
28
|
|
|
176
|
-
|
|
177
|
-
|
|
29
|
+
import {
|
|
30
|
+
Footer, GlobalStyles, ThemeProvider, ThemeType,
|
|
31
|
+
} from '@royaloperahouse/chord';
|
|
178
32
|
|
|
179
|
-
# Use the -u option to update snapshots if needed
|
|
180
|
-
# Run `yarn test:watch` to re-run tests on changes
|
|
181
|
-
```
|
|
182
33
|
|
|
183
|
-
|
|
34
|
+
const App = ({ children }: InnerProps): React.ReactElement => (
|
|
35
|
+
<ErrorBoundary>
|
|
36
|
+
<ThemeProvider theme={ThemeType.Core}>
|
|
37
|
+
<GlobalStyles />
|
|
38
|
+
<Wrapper>
|
|
39
|
+
<Header />
|
|
40
|
+
<GlobalStyle />
|
|
41
|
+
<HealthBanner />
|
|
42
|
+
<ErrorBoundary>
|
|
43
|
+
<Content>
|
|
44
|
+
{children}
|
|
45
|
+
</Content>
|
|
46
|
+
</ErrorBoundary>
|
|
47
|
+
<LiveChat />
|
|
48
|
+
</Wrapper>
|
|
49
|
+
<Footer data={footerData} />
|
|
50
|
+
</ThemeProvider>
|
|
51
|
+
</ErrorBoundary>
|
|
52
|
+
);
|
|
184
53
|
|
|
185
|
-
```bash
|
|
186
|
-
yarn test-storybook
|
|
187
|
-
# Use the -u option to update snapshots if needed
|
|
188
54
|
```
|
|
189
55
|
|
|
56
|
+
## Components
|
|
190
57
|
|
|
191
|
-
|
|
192
|
-
---
|
|
193
|
-
|
|
194
|
-
### **1. Branching Model**
|
|
195
|
-
* The Chord project lives in the `roh-components` *monorepo*
|
|
196
|
-
* When working on Chord, treat the `roh-components/packages/chord` directory as your root
|
|
197
|
-
* The Chord **development** branch is currently `chord-development`
|
|
198
|
-
* The Chord **main** branch is currently `chord-releases`
|
|
199
|
-
* All work should be done on a correctly named **feature branch** of the format: `issueType/ticketNumber-short-description-of-feature`, e.g. `feature/RD-1234-update-chord-documentation`
|
|
200
|
-
* Always create your feature branch FROM, and submit pull requests TO, the **main** branch
|
|
201
|
-
* For **QA / UAT** of a Chord component in isolation: following review you should deploy a preview version to Chromatic straight from your **feature branch** _without_ merging to development
|
|
202
|
-
* For releasing an **NPM snapshot**: merge your feature branch into the **development** branch and publish the NPM snapshot from there
|
|
203
|
-
|
|
204
|
-
### **2. Detailed Workflow**
|
|
205
|
-
|
|
206
|
-
#### **Before review:**
|
|
207
|
-
|
|
208
|
-
* Git pull the latest version of `chord-releases`
|
|
209
|
-
* Checkout a new, correctly-named feature branch from `chord releases`
|
|
210
|
-
* Do your work on this feature branch
|
|
211
|
-
* Run: `yarn lint`
|
|
212
|
-
* Run: `yarn test`
|
|
213
|
-
* Commit your changes
|
|
214
|
-
* Create a pull request from your feature branch to `chord-releases`
|
|
215
|
-
* Add the appropriate reviewers
|
|
216
|
-
|
|
217
|
-
#### **Before QA / UAT:**
|
|
218
|
-
|
|
219
|
-
After your PR is approved, you have two options:
|
|
220
|
-
|
|
221
|
-
**i.** For QA of a component in isolation:
|
|
222
|
-
|
|
223
|
-
* Follow the steps above in *Deploying the Storybook -> 2. Deploying a preview version remotely*
|
|
224
|
-
* Share the generated Chromatic URL with the appropriate people for QA / UAT
|
|
225
|
-
|
|
226
|
-
**ii.** For integrated testing of a component in the frontend staging environments:
|
|
227
|
-
|
|
228
|
-
* Check out the `chord-development` branch
|
|
229
|
-
* Merge your work in to `chord-development`
|
|
230
|
-
* Follow the steps above under *Publishing a New Package Version -> 1. To release a snapshot version*
|
|
231
|
-
* Git push the updated `chord-development` branch to remote
|
|
232
|
-
* Finally, in the frontend repo:
|
|
233
|
-
|
|
234
|
-
1. Update the `package.json` to reference the new snapshot version
|
|
235
|
-
2. Run: `yarn install`
|
|
236
|
-
3. Deploy the frontend to a staging environment
|
|
237
|
-
|
|
238
|
-
#### **When ready for production:**
|
|
239
|
-
|
|
240
|
-
* Return to your chord **feature branch**
|
|
241
|
-
* Update the chord version in `package.json`, incrementing from the last **stable** release, found in `chord-releases`, and following the rules described in the *Versioning* section
|
|
242
|
-
* Update `CHANGELOG.md`, adding the new version number and a short description of your changes
|
|
243
|
-
* Run: `yarn lint`
|
|
244
|
-
* Run: `yarn test`
|
|
245
|
-
* Run: `yarn test-storybook -u`
|
|
246
|
-
* Run: `yarn build-storybook`
|
|
247
|
-
* Git commit, push, and update your PR for final approval
|
|
248
|
-
* Merge your approved PR to `chord-releases`
|
|
249
|
-
* Follow the steps in *Publishing a New Package Version -> 2. To release a stable version* to publish the NPM package
|
|
250
|
-
* Finally, follow the steps in *Deploying The Storybook -> 3. To deploy a release version*, to update the public Chord Storybook page
|
|
251
|
-
|
|
252
|
-
Once you have successfully published a new release version, you can open a ticket to update to this version in any of the frontend repos.
|
|
253
|
-
|
|
254
|
-
|
|
255
|
-
## Notes
|
|
256
|
-
---
|
|
257
|
-
### The `storybook-static` folder
|
|
258
|
-
|
|
259
|
-
This folder contains all the HTML / JS required to deploy the Storybook as a static site. It's autogenerated whenever the Storybook is built and therefore will show up a lot of merge conflicts when you merge other branches into your feature branch. It is best to leave generating the storybook until the later part of your workflow, but in case you run into conflicts earlier, it's ok to just delete the folder and regenerate using:
|
|
260
|
-
|
|
261
|
-
```bash
|
|
262
|
-
yarn build-storybook
|
|
263
|
-
```
|
|
58
|
+
Accordion, Accordions, AltHeader, AnchorTabBar, AnnouncementBanner, BodyText, Card, Cards, Carousel, CinemaBadge, ContactCard, ControlledDropdown, devices, Editorial, Footer, GlobalStyles, Grid, GridItem, Header, HighlightsCarousel, HighlightsCarouselCinema, HighlightsCarouselCore, HighlightsCarouselStream, Icon, ImageWithCaption, Navigation, Overline, PageHeadingCinema, PageHeadingCore, PageHeadingImpact, PageHeadingStream, PeopleListing, PrimaryButton, PromoWithTags, PromoWithTitle, RotatorButtons, SecondaryButton, SecondaryLogo, SectionSplitter, SectionTitle, Sponsorship, StickyBar, StreamBadge, Subtitle, Tab, TabLink, Tabs, TertiaryButton, TextLink, TextOnly, Tickbox, TitleWithCTA, ThemeProvider, TypeTags, Quote
|
|
264
59
|
|
|
265
|
-
|
|
60
|
+
## Types
|
|
266
61
|
|
|
267
|
-
|
|
268
|
-
### Examples
|
|
62
|
+
AspectRatio, CarouselType, Colors, FooterData, INavigationProps, INavTopProps, TickboxMode, ThemeType
|
|
269
63
|
|
|
270
|
-
There is an example implementation in the example folder. Alternatively there are also integration examples in storybook. Make sure to keep these updated so as to showcase the current components available.
|
|
271
64
|
|
|
272
|
-
|
|
273
|
-
### Bundle analysis
|
|
65
|
+
## Documentation
|
|
274
66
|
|
|
275
|
-
|
|
67
|
+
See Storybook as a reference
|