v7.0.0-alpha.25

* added column dependency to row generator memo listeners

* added assertion to stop an infinite loop inside usePagination

.babelrc

@@ -0,0 +1,16 @@
+{
+  "presets": [
+    [
+      "@babel/preset-env",
+      {
+        "modules": false
+      }
+    ],
+    "@babel/react"
+  ],
+  "env": {
+    "test": {
+      "presets": ["@babel/preset-env", "@babel/react"]
+    }
+  }
+}

.eslintrc

@@ -0,0 +1,3 @@
+{
+  "extends": ["react-app", "prettier"]
+}

.eslintrc.js

@@ -1,3 +0,0 @@
-module.exports = {
-  extends: 'react-tools',
-}

.github/FUNDING.yml

@@ -0,0 +1,5 @@
+# These are supported funding model platforms
+
+github: tannerlinsley
+patreon: tannerlinsley
+custom: https://youtube.com/tannerlinsley

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,6 +4,14 @@ about: Create a report to help us improve
 
 ---
 
+# Using v6?
+
+v6 is now considered feature complete to its current abilities and limitations. We are not actively working to fix any issues for v6 any more. We will, however, merge any non-breaking pull requests submitted to fix anything in v6.
+
+# Using v7?
+
+Thanks for using the alpha version of React Table v7! We're very excited about it.
+
 **Describe the bug**
 A clear and concise description of what the bug is.
 
@@ -18,7 +26,7 @@ Steps to reproduce the behavior:
 A clear and concise description of what you expected to happen.
 
 **Codesandbox!**
-Use a new [react-table codesandbox](codesandbox.io/s/X6npLXPRW) to reproduce the issue.
+Use a new [react-table codesandbox](https://codesandbox.io/s/m5lxzzpz69) to reproduce the issue.
 
 **Screenshots**
 If applicable, add screenshots to help explain your problem.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -4,14 +4,6 @@ about: Suggest an idea for this project
 
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+# STOP
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-Add any other context or screenshots about the feature request here.
+We do not track feature requests through Github. Please use the [Spectrum React Table Forum](https://spectrum.chat/react-table) to talk about new ideas and features.

.github/ISSUE_TEMPLATE/questions--support---help.md

@@ -4,8 +4,8 @@ about: Looking for help? Need a question answered?
 
 ---
 
-STOP!!!
+# STOP
 
-Github issues is no place for general support. We encourage you to use our public support forum at https://spectrum.chat/react-table.
+We do not use Github to track general support. Please use our public support forum at https://spectrum.chat/react-table.
 
 NOTE: If a support/help/question issue is opened, it will be closed immediately and be redirected to the forum. Thanks for helping us keep our issues clean and productive!

.gitignore

@@ -1,6 +1,7 @@
-node_modules/
-lib/
-es/
+node_modules
+lib
+dist
+es
 docs/build
 react-table.js
 react-table.min.js
@@ -9,4 +10,3 @@ react-table.css
 .idea
 .DS_Store
 .history
-.vscode

.huskyrc.js

@@ -0,0 +1,6 @@
+module.exports = {
+  hooks: {
+    'pre-commit': 'lint-staged && yarn test:ci',
+    'commit-msg': 'commitlint -E HUSKY_GIT_PARAMS',
+  },
+}

.travis.yml

@@ -1,4 +1,7 @@
 language: node_js
 node_js:
-  - "6"
+  - "10"
+
+cache: yarn
+
 script: npm test

CHANGELOG.md

@@ -1,24 +1,3 @@
-## 6.10.3
-
-- Further improve `normalizeComponent` function
-
-## 6.10.2
-
-- Fixed regression found in `normalizeComponent` function fix
-
-## 6.10.1
-
-- Fixed issues with `normalizeComponent` function
-
-## 6.10.0
-
-- Rebased volatile commits out of 6.9.0
-- Merged (hopefully) non-breaking fixes after rebasing and reverting.
-
-## 6.9.0
-
-This version has been reverted due to some major bugs that were introduced with it.
-
 ## 6.8.6
 
 #### Fixes & Optimizations

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at TANNERLINSLEY@GMAIL.COM. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# Contributing
+
+## Questions
+
+If you have questions about implementation details, help or support, then please use our dedicated community forum at [Spectrum.chat/react-table](https://spectrum.chat/react-table) **PLEASE NOTE:** If you choose to instead open an issue for your question, your issue will be immediately closed and redirected to the forum.
+
+## Reporting Issues
+
+If you have found what you think is a bug, please [file an issue](https://github.com/tannerlinsley/react-table/issues/new). **PLEASE NOTE:** Issues that are identified as implementation questions or non-issues will be immediately closed and redirected to [Spectrum.chat/react-table](https://spectrum.chat/react-table)
+
+## Suggesting new features
+
+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.
+
+## Development
+
+If you have been assigned to fix an issue or develop a new feature, please follow these steps to get started:
+
+- Fork this repository
+- Install dependencies by running `$ yarn`
+- Link `react-table` locally by running `$ yarn link`
+- Auto-build files as you edit by running `$ yarn start`
+- Implement your changes and tests to files in the `src/` directory and corresponding test files
+- To run examples, follow their individual directions. Usually this is just `$ yarn && yarn start`.
+- To run examples using your local build, link to the local `react-table` by running `$ yarn link react-table` from the example's directory
+- Document your changes in the root `README.md`
+- To stage a commit, run `yarn commit`
+- Submit PR for review

archives/v6-examples/react-table-100k-rows-aggregation/package.json

@@ -20,4 +20,4 @@
     "test": "react-scripts test --env=jsdom",
     "eject": "react-scripts eject"
   }
-}
+}