Skip to content

Commit c5739f5

Browse files
tannerlinsleytannerlinsley
committed
Boom
1 parent a0f41ca commit c5739f5

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

47 files changed

+20088
-0
lines changed

‎.all-contributorsrc

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
{
2+
"projectName": "react-virtual",
3+
"projectOwner": "tannerlinsley",
4+
"repoType": "github",
5+
"repoHost": "https://github.com",
6+
"files": [
7+
"README.md"
8+
],
9+
"imageSize": 100,
10+
"commit": false,
11+
"commitConvention": "none",
12+
"contributors": [
13+
{
14+
"login": "tannerlinsley",
15+
"name": "Tanner Linsley",
16+
"avatar_url": "https://avatars0.githubusercontent.com/u/5580297?v=4",
17+
"profile": "https://tannerlinsley.com",
18+
"contributions": [
19+
"code",
20+
"ideas",
21+
"example",
22+
"maintenance",
23+
"review"
24+
]
25+
},
26+
],
27+
"contributorsPerLine": 7,
28+
"skipCi": true
29+
}

‎.babelrc

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
{
2+
"presets": [
3+
[
4+
"@babel/env",
5+
{
6+
"modules": false,
7+
"loose": true,
8+
"exclude": ["@babel/plugin-transform-regenerator"]
9+
}
10+
],
11+
"@babel/react"
12+
],
13+
"plugins": ["babel-plugin-transform-async-to-promises"],
14+
"env": {
15+
"test": {
16+
"presets": [
17+
[
18+
"@babel/env",
19+
{
20+
"modules": "commonjs",
21+
"loose": true,
22+
"exclude": ["@babel/plugin-transform-regenerator"]
23+
}
24+
]
25+
]
26+
}
27+
}
28+
}

‎.browserslistrc

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Browsers we support
2+
> 0.5%
3+
Chrome >= 73
4+
ChromeAndroid >= 75
5+
Firefox >= 67
6+
Edge >= 17
7+
IE 11
8+
Safari >= 12.1
9+
iOS >= 11.3

‎.editorconfig

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
root = true
2+
3+
[*]
4+
charset = utf-8
5+
indent_style = space
6+
indent_size = 2
7+
end_of_line = lf
8+
insert_final_newline = true
9+
trim_trailing_whitespace = true

‎.eslintrc

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"parser": "babel-eslint",
3+
"extends": ["react-app", "prettier"],
4+
"env": {
5+
"es6": true
6+
},
7+
"parserOptions": {
8+
"sourceType": "module"
9+
}
10+
}

‎.github/FUNDING.yml

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
github: tannerlinsley
2+
custom: https://youtube.com/tannerlinsley

‎.github/workflows/size-comments.yml

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
name: Compressed Size
2+
3+
on: [pull_request]
4+
5+
jobs:
6+
build:
7+
runs-on: ubuntu-latest
8+
9+
steps:
10+
- uses: actions/checkout@v2-beta
11+
with:
12+
fetch-depth: 1
13+
- uses: preactjs/compressed-size-action@v1
14+
with:
15+
repo-token: '${{ secrets.GITHUB_TOKEN }}'

‎.github/workflows/test-and-publish.yml

+46
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
name: react-virtual tests
2+
3+
on:
4+
push:
5+
branches:
6+
- 'master'
7+
pull_request:
8+
9+
jobs:
10+
test:
11+
name: 'node ${{ matrix.node }} ${{ matrix.os }} '
12+
runs-on: '${{ matrix.os }}'
13+
strategy:
14+
matrix:
15+
os: [ubuntu-latest]
16+
node: [12, 10]
17+
steps:
18+
- uses: actions/setup-node@v1
19+
with:
20+
node-version: ${{ matrix.node }}
21+
- uses: actions/checkout@v2
22+
with:
23+
fetch-depth: 1
24+
- run: npm i -g yarn
25+
- run: yarn --frozen-lockfile
26+
- run: yarn test:ci
27+
28+
publish-module:
29+
name: 'Publish Module to NPM'
30+
needs: test
31+
if: github.ref == 'refs/heads/master' #publish only when merged in master, not on PR
32+
runs-on: ubuntu-latest
33+
steps:
34+
- uses: actions/checkout@v2
35+
with:
36+
fetch-depth: 1
37+
- uses: actions/setup-node@v1
38+
with:
39+
node-version: 12
40+
registry-url: https://registry.npmjs.org/
41+
- run: npm i -g yarn
42+
- run: yarn --frozen-lockfile
43+
- run: npx semantic-release@17
44+
env:
45+
NODE_AUTH_TOKEN: ${{secrets.npm_token}}
46+
GH_TOKEN: ${{secrets.GH_TOKEN}}

‎.gitignore

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
2+
# See https://help.github.com/ignore-files/ for more about ignoring files.
3+
4+
# dependencies
5+
node_modules
6+
7+
# builds
8+
build
9+
dist
10+
artifacts
11+
.rpt2_cache
12+
coverage
13+
14+
# misc
15+
.DS_Store
16+
.env
17+
.env.local
18+
.env.development.local
19+
.env.test.local
20+
.env.production.local
21+
.next
22+
23+
npm-debug.log*
24+
yarn-debug.log*
25+
yarn-error.log*
26+
.history
27+
size-plugin.json
28+
stats.html

‎.vscode/settings.json

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"workbench.colorCustomizations": {
3+
"titleBar.activeBackground": "#885cff", // change this color!
4+
"titleBar.inactiveBackground": "#885cff", // change this color!
5+
"titleBar.activeForeground": "#ffffff", // change this color!
6+
"titleBar.inactiveForeground": "#ffffff" // change this color!
7+
}
8+
}

‎CONTRIBUTING.md

+114
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
# Contributing
2+
3+
## Questions
4+
5+
If you have questions about implementation details, help or support, then please use our dedicated community forum at [Github Discussions](https://github.com/tannerlinsley/react-virtual/discussions) **PLEASE NOTE:** If you choose to instead open an issue for your question, your issue will be immediately closed and redirected to the forum.
6+
7+
## Reporting Issues
8+
9+
If you have found what you think is a bug, please [file an issue](https://github.com/tannerlinsley/react-virtual/issues/new). **PLEASE NOTE:** Issues that are identified as implementation questions or non-issues will be immediately closed and redirected to [Github Discussions](https://github.com/tannerlinsley/react-virtual/discussions)
10+
11+
## Suggesting new features
12+
13+
If you are here to suggest a feature, first create an issue if it does not already exist. From there, we will discuss use-cases for the feature and then finally discuss how it could be implemented.
14+
15+
## Development
16+
17+
If you have been assigned to fix an issue or develop a new feature, please follow these steps to get started:
18+
19+
- Fork this repository
20+
- Install dependencies by running `$ yarn`
21+
- Link `react-virtual` locally by running `$ yarn link`
22+
- Auto-build files as you edit by running `$ yarn start`
23+
- Implement your changes and tests to files in the `src/` directory and corresponding test files
24+
- To run examples, follow their individual directions. Usually this is just `$ yarn && yarn start`.
25+
- To run examples using your local build, link to the local `react-virtual` by running `$ yarn link react-virtual` from the example's directory
26+
- Document your changes in the appropriate doc page
27+
- Git stage your required chnages and commit (see below commit guidelines)
28+
- Submit PR for review
29+
30+
## Commit message conventions
31+
32+
`react-virtual` is using [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines).
33+
34+
We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**.
35+
36+
### Commit Message Format
37+
38+
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
39+
format that includes a **type**, a **scope** and a **subject**:
40+
41+
```
42+
<type>(<scope>): <subject>
43+
<BLANK LINE>
44+
<body>
45+
<BLANK LINE>
46+
<footer>
47+
```
48+
49+
The **header** is mandatory and the **scope** of the header is optional.
50+
51+
Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
52+
53+
### Type
54+
55+
Must be one of the following:
56+
57+
- **feat**: A new feature
58+
- **fix**: A bug fix
59+
- **docs**: Documentation only changes
60+
- **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
61+
semi-colons, etc)
62+
- **refactor**: A code change that neither fixes a bug nor adds a feature
63+
- **perf**: A code change that improves performance
64+
- **test**: Adding missing or correcting existing tests
65+
- **chore**: Changes to the build process or auxiliary tools and libraries such as documentation
66+
generation
67+
68+
### Scope
69+
70+
The scope could be anything specifying place of the commit change. For example `useQuery`, `useMutation` etc...
71+
72+
You can use `*` when the change affects more than a single scope.
73+
74+
### Subject
75+
76+
The subject contains succinct description of the change:
77+
78+
- use the imperative, present tense: "change" not "changed" nor "changes"
79+
- don't capitalize first letter
80+
- no dot (.) at the end
81+
82+
### Body
83+
84+
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
85+
86+
### Footer
87+
88+
The footer should contain any information about **Breaking Changes** and is also the place to [reference GitHub issues that this commit closes](https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue).
89+
90+
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
91+
92+
### Example
93+
94+
Here is an example of the release type that will be done based on a commit messages:
95+
96+
| Commit message | Release type |
97+
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------- |
98+
| `fix(pencil): stop graphite breaking when too much pressure applied` | Patch Release |
99+
| `feat(pencil): add 'graphiteWidth' option` | ~~Minor~~ Feature Release |
100+
| `perf(pencil): remove graphiteWidth option`<br><br>`BREAKING CHANGE: The graphiteWidth option has been removed.`<br>`The default graphite width of 10mm is always used for performance reasons.` | ~~Major~~ Breaking Release |
101+
102+
### Revert
103+
104+
If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
105+
106+
## Pull requests
107+
108+
Maintainers merge pull requests by squashing all commits and editing the commit message if necessary using the GitHub user interface.
109+
110+
Use an appropriate commit type. Be especially careful with breaking changes.
111+
112+
## Releases
113+
114+
For each new commit added to `master` with `git push` or by merging a pull request or merging from another branch, a github action is triggered and runs the `semantic-release` command to make a release if there are codebase changes since the last release that affect the package functionalities.

‎LICENSE

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2019 Tanner Linsley
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

0 commit comments

Comments
 (0)