1 | ## Pull Request Guidelines
|
2 |
|
3 | - Fork this repository to your own account. Do not create branches here.
|
4 | - **DO NOT** include files inside `dist` directory.
|
5 | - Rebase before creating a PR to keep commit history clear.
|
6 | - Make sure that running `yarn build` output do not emit any warnings or errors
|
7 |
|
8 | ### When adding/modifying/renaming any attribute method or event
|
9 | **MUST HAVE**
|
10 | - Must be supported with an issue and provide little description about it, including the name, allowed values, defaults etc
|
11 | - Add relevant documentation in `./docs/api.html`
|
12 |
|
13 | **NICE TO HAVE**
|
14 | - If adding new dependency, be considerate of the bundle size since we bundle everything in a single file (`rapidoc-min.js`), like to keep its size down
|
15 | - It is a good idea to show case it using an example
|
16 | - examples go under `./docs/examples` folder
|
17 | - if your example is using a new spec then add in `./docs/specs` folder
|
18 | - include a reference to the example in `./docs/list.html` file
|
19 |
|
20 | ## Prerequisites
|
21 | `Node 10.15.3+` and `yarn 1.22.4+` and `npm 6.14.4+` are required. Note: we use yarn to lock dependency versions, so you should install dependencies using `yarn` instead of `npm`.
|
22 |
|
23 | For development
|
24 | ```shell
|
25 | git clone https://github.com/rapi-doc/RapiDoc.git
|
26 | yarn install
|
27 | yarn serve
|
28 | # open http://localhost:8080
|
29 | ```
|
30 |
|
31 | To Generate Production bundle:
|
32 | ```shell
|
33 | yarn build
|
34 | # yarn build_windows (if you use windows)
|
35 | ```
|