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
name: Test plot-schema.json diff - If failed, after (npm start) you could run (npm run schema && git add test/plot-schema.json && git commit -m "update plot-schema diff")
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,14 @@ Thanks for your interest in plotly.js!
9
9
### Features, Bug fixes, and others:
10
10
11
11
Before opening a pull request, developer should:
12
+
1. make sure they are not on the `master` branch of their fork as using `master` for a pull request would make it difficult to fetch `upstream` changes.
13
+
2. fetch latest changes from `upstream/master` into your fork i.e. `origin/master` then pull `origin/master` from you local `master`.
14
+
3. then `git rebase master` their local dev branch off the latest `master` which should be sync with `upstream/master` at this time.
15
+
4. make sure to **not**`git add` the `dist/` folder (the `dist/` is updated only on version bumps).
16
+
5. make sure to commit changes to the `package-lock.json` file (if any new dependency required).
17
+
6. provide a title and write an overview of what the PR attempts to do with a link to the issue they are trying to address.
18
+
7. select the _Allow edits from maintainers_ option (see this [article](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) for more details).
12
19
13
-
-`git rebase` their local branch off the latest `master`,
14
-
- make sure to **not**`git add` the `dist/` folder (the `dist/` is updated only on version bumps),
15
-
- make sure to commit changes to the `package-lock.json` file (if any new dependency required),
16
-
- write an overview of what the PR attempts to do,
17
-
- select the _Allow edits from maintainers_ option (see this [article](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) for more details).
18
-
19
-
Note that it is forbidden to force push (i.e. `git push -f`) to remote branches associated with opened pull requests. Force pushes make it hard for maintainers to keep track of updates. Therefore, if required, please `git merge master` into your PR branch instead of `git rebase master`.
20
+
After opening a pull request, developer:
21
+
- should create a new small markdown log file using the PR number e.g. `1010_fix.md` or `1010_add.md` inside `draftlogs` folder as described in this [README](https://github.com/plotly/plotly.js/blob/master/draftlogs/README.md), commit it and push.
22
+
- should **not** force push (i.e. `git push -f`) to remote branches associated with opened pull requests. Force pushes make it hard for maintainers to keep track of updates. Therefore, if required, please fetch `upstream/master` and "merge" with master instead of "rebase".
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+43-15Lines changed: 43 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,14 +138,19 @@ Three additional helpers exist that are refreshed every second:
138
138
There is also a search bar in the top right of the dashboard. This fuzzy-searches
139
139
image mocks based on their file name and trace type.
140
140
141
-
#### Alternative to test dashboard
141
+
#### Step 5: Regenerate plot-schema in "test" folder then review & commit potential changes
142
142
143
-
Use the [`plotly-mock-viewer`](https://github.com/rreusser/plotly-mock-viewer)
144
-
which has live-reloading and a bunch of other cool features.
145
-
An online version of `plotly-mock-viewer` is available at <https://rreusser.github.io/plotly-mock-viewer/>
146
-
which uses <https://cdn.plot.ly/plotly-latest.min.js>
143
+
```bash
144
+
npm run schema
145
+
```
146
+
147
+
#### Step 6: Review & commit potential changes made to test/plot-schema.json
147
148
148
-
#### Other npm scripts
149
+
> If you are editing attribute descriptions or implementing a new feature this file located in the test folder records the proposed changes to the API. Note that there is another plot-schema.json file located in the dist folder, which should only be updated by the maintainers at release time.
150
+
151
+
**IMPORTANT:** please do not change and commit any files in the "dist" folder
152
+
153
+
#### Other npm scripts that may be of interest in development
149
154
150
155
-`npm run preprocess`: pre-processes the css and svg source file in js. This
151
156
script must be run manually when updating the css and svg source files.
@@ -207,17 +212,40 @@ npm run test-jasmine -- --help
207
212
npm run test-jasmine -- --info
208
213
```
209
214
210
-
### Draft new baseline
211
-
Install fonts and tools
215
+
### Draft new baselines
216
+
#### With docker:
217
+
> If you prefer using docker each time you need to
218
+
```sh
219
+
docker run -it -v "$(pwd)":/plotly.js circleci/python:3.8.9 bash
> Please note that as of v2 the "plotly-latest" outputs (e.g. https://cdn.plot.ly/plotly-latest.min.js) will no longer be updated on the CDN, and will stay at the last v1 patch v1.58.4. Therefore, to use the CDN with plotly.js v2 and higher, you must specify an exact plotly.js version.
88
+
> Please note that as of v2 the "plotly-latest" outputs (e.g. https://cdn.plot.ly/plotly-latest.min.js) will no longer be updated on the CDN, and will stay at the last v1 patch v1.58.5. Therefore, to use the CDN with plotly.js v2 and higher, you must specify an exact plotly.js version.
89
89
90
90
To support MathJax, you need to load version two of MathJax e.g. `v2.7.5` files from CDN or npm.
0 commit comments