Skip to content

Commit 788e11c

Browse files
authored
Merge pull request #2778 from finos/update-docs
Update documentation for `3.x`
2 parents 13b26d7 + 8a01cac commit 788e11c

114 files changed

Lines changed: 2156 additions & 2639 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 112 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,126 @@
11
---
2-
name: 🐛 Bug Report
3-
about: If something isn't working as expected 🤔.
4-
2+
name: Bug Report
3+
about: If something isn't working as expected.
54
---
65

76
## Bug Report
87

98
### Steps to Reproduce:
10-
1. ...step 1 description...
11-
2. ...step 2 description...
12-
3. ...step 3 description...
9+
10+
Please provide a full reproduction of the issue. There are three ways we accept
11+
repros:
12+
13+
1. If the issue you are reporting is a UX/UI issue which can be recreated by
14+
visiting a Perspective demo _hosted by the project itself_, and any dataset
15+
required to reproduce the error can be included in the report. In this case,
16+
please provide detailed step-by-step instructions on how to reproduce,
17+
including any screenshots which help illustrate, as well as including any
18+
fully-encoded test data we may need.
19+
20+
2. If you are reporting a build or installation issue with the library itself,
21+
which can be recreated from a shell. In this case, please provided detailed
22+
code blocks describing how you tried to install, which commands were issued,
23+
including and dependencies you needed to install and hwo you installed them.
24+
25+
3. If you are reporting a _anything else_, including but not limited to:
26+
27+
- Build issues which require _any_ metadata files e.g. a `package.json`,
28+
`Cargo.toml`, etc
29+
- Bundler or packaging errors with JavaScript
30+
- Library functions which return the wrong results or error
31+
- CPU or memory usage performance regressions, or regressions in thread
32+
utilization
33+
34+
In this case, we require a _complete reproduction_ of the issue in the form
35+
of a repository. Quoting this exceptional definition from
36+
[@Rich-Harris's micro-essay on Repros](https://gist.github.com/Rich-Harris/88c5fc2ac6dc941b22e7996af05d70ff),
37+
please follow these guidelines:
38+
39+
> 1. Create a sample repo on GitHub (or wherever)
40+
> 2. Demonstrate the problem, and nothing but the problem. If the app where
41+
> you're experiencing the issue happens to use Gulp, I don't care,
42+
> unless the problem involves Gulp. Remove that stuff. Whittle it down
43+
> to the _bare minimum_ of code that reliably demonstrates the issue.
44+
> Get rid of any dependencies that aren't _directly_ related to the
45+
> problem.
46+
> 3. Install all your dependencies to `package.json`. If I can't clone the
47+
> repo and do `npm install && npm run build` (or similar – see point 4)
48+
> to see the problem, because I need some globally installed CLI tool or
49+
> whatever, then you've made it harder to get to the bottom of the
50+
> issue.
51+
> 4. Include instructions in the repo, along with a description of the
52+
> expected and actual behaviour. Obviously the issue should include
53+
> information about the bug as well, but it's really helpful if
54+
> `README.md` includes that information, plus a link back to the issue.
55+
> If there are any instructions beyond `npm install && npm run build`,
56+
> they should go here.
57+
58+
Some examples which _do not_ qualify as _complete_ and are mostly useless to
59+
us for debugging:
60+
61+
- Instructions which ask us to visit a website or download an application,
62+
even if it is _completely_ open source (and expecially if it is not)
63+
- Instructions which just describe how to create a project, e.g. with a
64+
specific build tool or template
65+
- Screenshots of exceptions
66+
- Screenshots of code
67+
- Code snippets copied from a larger application context
1368

1469
### Expected Result:
15-
...description of what you expected to see...
70+
71+
Describe what you expected to see. If you are reporting a UX/UI error, this may
72+
include screenshots with annotations.
1673

1774
### Actual Result:
18-
...what actually happened, including full exceptions (please include the entire stack trace, including "caused by" entries), log entries, screen shots etc. where appropriate...
75+
76+
Describe what actually happened, with special attention to the errant behavior.
77+
Always include:
78+
79+
- OS and version
80+
- Platform/language + version
81+
82+
If you are reporting a UX/UI error:
83+
84+
- (if websocket) Platform/language + version of remote perspective server.
85+
- Full exception/error message if applicable.
86+
- Any potentially relevent JavaScript developer console error logs.
87+
- Screenshots of the UI in an obviously broken state. (but please try to avoid
88+
screenshots of your code, see below)
89+
90+
If you are reporting a library error:
91+
92+
- (if websocket) Platform/language + version of remote perspective server.
93+
- Full exception error capture (please include the entire stack trace,
94+
including "caused by" entries), log entries, etc. where appropriate. Please
95+
avoid posting screenshots of code (which we may need to debug).
96+
97+
If you are reporting a build or install error:
98+
99+
- Full error output from running your repro, formatted as a code block (please
100+
_do not_ include screenshots of build logs).
19101

20102
### Environment:
21-
...version and build of the project, OS and runtime versions, virtualised environment (if any), etc. ...
103+
104+
For JavaScript (browser):
105+
106+
- `@finos/perspective` version
107+
- Browser and version
108+
- OS
109+
- (if websocket) Language/version/OS of perspective server
110+
111+
For Node.js:
112+
113+
- `node` version
114+
- OS
115+
116+
For Python
117+
118+
- `python` interpreter version (Only CPython).
119+
- package manager and version (conda/pip/\*)
120+
- Are you compiling from an sdist of wheel?
121+
- Platform and version (Jupyter/tornado/lib/\*)
122+
- OS
22123

23124
### Additional Context:
24-
...add any other context about the problem here. If applicable, add screenshots to help explain...
125+
126+
Add any other context about the problem here.
Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,22 @@
11
---
2-
name: 🚀 Feature Request
3-
about: I have a suggestion (and may want to implement it 🙂)!
4-
2+
name: Feature Request
3+
about: I have a suggestion.
54
---
65

76
## Feature Request
87

98
### Description of Problem:
10-
...what *problem* are you trying to solve that the project doesn't currently solve?
119

12-
...please resist the temptation to describe your request in terms of a solution. Job Story form ("When [triggering condition], I want to [motivation/goal], so I can [outcome].") can help ensure you're expressing a problem statement.
10+
...what _problem_ are you trying to solve that the project doesn't currently
11+
solve?
12+
13+
...please resist the temptation to describe your request in terms of a solution.
14+
Job Story form ("When [triggering condition], I want to [motivation/goal], so I
15+
can [outcome].") can help ensure you're expressing a problem statement.
1316

1417
### Potential Solutions:
15-
...clearly and concisely describe what you want to happen. Add any considered drawbacks.
18+
19+
...clearly and concisely describe what you want to happen. Add any considered
20+
drawbacks.
1621

1722
... if you've considered alternatives, clearly and concisely describe those too.

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
### Pull Request Checklist
2+
3+
- [ ] Description which clearly states what problems the PR solves.
4+
- [ ] Description contains a link to the Github Issue, and any relevent
5+
Discussions, this PR applies to.
6+
- [ ] Include new tests that fail without this PR but passes with it.
7+
- [ ] Include any relevent Documentation changes related to this change.
8+
- [ ] Verify all commits have been _signed_ in accordance with the DCO policy.
9+
- [ ] Reviewed PR commit history to remove unnecessary changes.
10+
- [ ] Make sure your PR passes _build_, _test_ and _lint_ steps _completely_.

.github/PULL_REQUEST_TEMPLATE/Bugfix.md

Lines changed: 0 additions & 28 deletions
This file was deleted.

.github/PULL_REQUEST_TEMPLATE/Documentation.md

Lines changed: 0 additions & 33 deletions
This file was deleted.

.github/PULL_REQUEST_TEMPLATE/Feature.md

Lines changed: 0 additions & 54 deletions
This file was deleted.

.github/actions/install-deps/action.yaml

Lines changed: 18 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,9 @@ inputs:
3232
python:
3333
default: "true"
3434
description: "Install Python dependencies?"
35+
playwright:
36+
default: "false"
37+
description: "Install browsers for playwright testing"
3538
clean:
3639
default: "false"
3740
description: "Clean unused deps. This is helpful if we run out of HD but slow!"
@@ -48,7 +51,7 @@ runs:
4851
using: "composite"
4952
steps:
5053
- name: Clean System
51-
uses: AdityaGarg8/remove-unwanted-software@v3
54+
uses: AdityaGarg8/remove-unwanted-software@v4.1
5255
if: ${{ inputs.clean == 'true' && runner.os != 'Windows' }}
5356
with:
5457
remove-android: "true"
@@ -117,13 +120,25 @@ runs:
117120
vcpkg.exe integrate install
118121
echo "VCPKG_INSTALLATION_ROOT=${env:VCPKG_INSTALLATION_ROOT}"
119122
echo "VCPKG_INSTALLATION_ROOT=${env:VCPKG_INSTALLATION_ROOT}" >> $env:GITHUB_OUTPUT
123+
echo "${env:VCPKG_INSTALLATION_ROOT}" >> $env:GITHUB_PATH
124+
echo "VCPKG_ROOT=${env:VCPKG_INSTALLATION_ROOT}" >> $env:GITHUB_ENV
120125
dir env:
121126
env:
122127
PYTHON_VERSION: ${{ matrix.python-version }}
123128
VCPKG_DEFAULT_TRIPLET: x64-windows
124129
VCPKG_PLATFORM_TOOLSET: v143
125130
if: ${{ runner.os == 'Windows' && inputs.cpp == 'true' }}
126131

132+
# https://github.com/apache/arrow/issues/38391
133+
- if: ${{ runner.os == 'macOS' }}
134+
shell: bash
135+
run: echo "MACOSX_DEPLOYMENT_TARGET=$(sw_vers -productVersion)" >> $GITHUB_ENV
136+
137+
# Use python 3.9 from manylinu
138+
- run: echo "/opt/python/cp39-cp39/bin" >> $GITHUB_PATH
139+
shell: bash
140+
if: ${{ runner.os == 'Linux' }}
141+
127142
- name: Set up Python ${{ matrix.python-version }}
128143
uses: actions/setup-python@v5
129144
if: ${{ inputs.python == 'true' && runner.os != 'Linux' }}
@@ -179,12 +194,12 @@ runs:
179194

180195
- name: Install JS dependencies
181196
shell: bash
182-
if: ${{ inputs.javascript == 'true' }}
197+
if: ${{ inputs.javascript == 'true' && inputs.playwright == 'true' }}
183198
run: pnpm install
184199

185200
- name: Install JS dependencies
186201
shell: bash
187-
if: ${{ inputs.javascript == 'false' }}
202+
if: ${{ inputs.javascript == 'false' || inputs.playwright == 'false'}}
188203
run: pnpm install --ignore-scripts
189204

190205
- name: Install Python dependencies

0 commit comments

Comments
 (0)