tabulator-tables 5.4.3 → 5.4.4

package/.babelrc.json

@@ -1,3 +1,3 @@
-{
-  "presets": [["@babel/env", { "modules": false }]],
-}
+{
+  "presets": [["@babel/env", { "modules": false }]],
+}

package/.editorconfig

@@ -1,6 +1,6 @@
-root = true
-
-[*]
-indent_style = tab
-end_of_line = lf
-insert_final_newline = true
+root = true
+
+[*]
+indent_style = tab
+end_of_line = lf
+insert_final_newline = true

package/.eslintignore

@@ -1,3 +1,3 @@
-.eslintrc.js
-dist
-examples
+.eslintrc.js
+dist
+examples

package/.eslintrc.js

@@ -1,28 +1,28 @@
-module.exports = {
-	"env": {
-		"browser": true,
-		"es2021": true,
-		"node": true, 
-		"amd": true,
-	},
-	globals: {
-		'luxon': 'readonly',
-		'XLSX': 'readonly',
-		'jspdf': 'readonly'
-	},
-	"extends": "eslint:recommended",
-	"parserOptions": {
-		"ecmaVersion": "latest",
-		"sourceType": "module"
-	},
-	"rules": {
-		"semi": "error",
-		"indent": ["error", "tab", {VariableDeclarator:0, "SwitchCase": 1}],
-		"no-unused-vars": ["warn", { "vars": "all", "args": "none", "ignoreRestSiblings": false }],
-		"no-fallthrough": "off",
-		"no-inner-declarations": "off",
-		"no-prototype-builtins": "off",
-		"no-empty": ["error", { "allowEmptyCatch": true }],
-		// "curly": "error",
-	}
-}
+module.exports = {
+	"env": {
+		"browser": true,
+		"es2021": true,
+		"node": true, 
+		"amd": true,
+	},
+	globals: {
+		'luxon': 'readonly',
+		'XLSX': 'readonly',
+		'jspdf': 'readonly'
+	},
+	"extends": "eslint:recommended",
+	"parserOptions": {
+		"ecmaVersion": "latest",
+		"sourceType": "module"
+	},
+	"rules": {
+		"semi": "error",
+		"indent": ["error", "tab", {VariableDeclarator:0, "SwitchCase": 1}],
+		"no-unused-vars": ["warn", { "vars": "all", "args": "none", "ignoreRestSiblings": false }],
+		"no-fallthrough": "off",
+		"no-inner-declarations": "off",
+		"no-prototype-builtins": "off",
+		"no-empty": ["error", { "allowEmptyCatch": true }],
+		// "curly": "error",
+	}
+}

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,58 +1,58 @@
----
-name: Bug report
-about: Report a bug with Tabulator
-title: ''
-labels: Possible Bug
-assignees: ''
-
----
-
-<!--
-YOUR BUG REPORT MUST CONTAIN A LINK TO A JSFiddle OR Codepen THAT DEMONSTRATES THE ISSUE OR IT WILL BE CLOSED WITHOUT DISCUSSION
-
-Please read the Bug Reporting Guide before completing this issue: http://tabulator.info/community/bug
-
-Please make sure you fill in all the sections of this template to give us the best chance of helping you
--->
-
-**Describe the bug**
-A clear and concise description of what the bug is.
-
-**Tabulator Info**
-- Which version of Tabulator are you using?
-
-**Working Example**
-YOU MUST include a link to a JS Fiddle or Codepen that demonstrates the problem, it is very hard to diagnose an issue from a simple description.
-<!--
-Please read the Minimal Reproducable Example guide if you are unsure what the example should look like http://tabulator.info/community/mre
-A quick guide on creating a JS Fiddle can be found on the Tabulator website http://tabulator.info/community/jsfiddle
-
-ISSUES CREATED WITHOUT THIS EXAMPLE WILL BE CLOSED WITHOUT DISCUSSION
--->
-
-**To Reproduce**
-A step by step guide to recreate the issue in your JS Fiddle or Codepen:
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
-
-**Expected behavior**
-A clear and concise description of what you expected to happen.
-
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
-
-**Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
-
-**Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
-
-**Additional context**
-Add any other context about the problem here.
+---
+name: Bug report
+about: Report a bug with Tabulator
+title: ''
+labels: Possible Bug
+assignees: ''
+
+---
+
+<!--
+YOUR BUG REPORT MUST CONTAIN A LINK TO A JSFiddle OR Codepen THAT DEMONSTRATES THE ISSUE OR IT WILL BE CLOSED WITHOUT DISCUSSION
+
+Please read the Bug Reporting Guide before completing this issue: http://tabulator.info/community/bug
+
+Please make sure you fill in all the sections of this template to give us the best chance of helping you
+-->
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Tabulator Info**
+- Which version of Tabulator are you using?
+
+**Working Example**
+YOU MUST include a link to a JS Fiddle or Codepen that demonstrates the problem, it is very hard to diagnose an issue from a simple description.
+<!--
+Please read the Minimal Reproducable Example guide if you are unsure what the example should look like http://tabulator.info/community/mre
+A quick guide on creating a JS Fiddle can be found on the Tabulator website http://tabulator.info/community/jsfiddle
+
+ISSUES CREATED WITHOUT THIS EXAMPLE WILL BE CLOSED WITHOUT DISCUSSION
+-->
+
+**To Reproduce**
+A step by step guide to recreate the issue in your JS Fiddle or Codepen:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/documentation.md

@@ -1,14 +1,14 @@
----
-name: Documentation
-about: Report an issue with the documentation on the tabulator.info website
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Website Page**
-A link to the page with the issue
-
-**Describe the issue**
-A clear and concise description of what the issue is.
+---
+name: Documentation
+about: Report an issue with the documentation on the tabulator.info website
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Website Page**
+A link to the page with the issue
+
+**Describe the issue**
+A clear and concise description of what the issue is.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,24 +1,24 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: Suggested Feature
-assignees: ''
-
----
-
-<!--
-Please read the Feature Requesting Guide before completing this issue: http://tabulator.info/community/feature
--->
-
-*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 [...]
-
-**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.
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: Suggested Feature
+assignees: ''
+
+---
+
+<!--
+Please read the Feature Requesting Guide before completing this issue: http://tabulator.info/community/feature
+-->
+
+*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 [...]
+
+**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.

package/.github/ISSUE_TEMPLATE/question.md

@@ -1,12 +1,12 @@
----
-name: Question (QUESTIONS MUST BE ASKED ON STACK OVERFLOW!!! DO NOT CREATE AN ISSUE!!!)
-about: Please ask questions on Stack Overflow, NOT on GitHub
-title: ''
-labels: Invalid, Question - Ask On Stack Overflow
-assignees: ''
-
----
-
-Please ask questions on www.stackoverflow.com the issues list is now reserved for feature requests and bug reports.
-
-Questions asked in the issue list will be automatically closed!
+---
+name: Question (QUESTIONS MUST BE ASKED ON STACK OVERFLOW!!! DO NOT CREATE AN ISSUE!!!)
+about: Please ask questions on Stack Overflow, NOT on GitHub
+title: ''
+labels: Invalid, Question - Ask On Stack Overflow
+assignees: ''
+
+---
+
+Please ask questions on www.stackoverflow.com the issues list is now reserved for feature requests and bug reports.
+
+Questions asked in the issue list will be automatically closed!

package/.github/workflows/bad-files-check.yml

@@ -1,39 +1,39 @@
-name: Bad files check
-on:
-  pull_request:
-
-jobs:
-  check:
-    name: Dist check
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out Git repository
-        uses: actions/checkout@v2
-        with:
-          fetch-depth: 0
-
-
-      - name: Get specific changed files in dist
-        id: changed-files-specific
-        uses: tj-actions/changed-files@v17.3
-        with:
-          files: |
-            dist
-
-      - name: Check file existence
-        id: check_files
-        uses: andstor/file-existence-action@v1
-        with:
-          files: "yarn.lock"
-
-      - name: Fail if dist files changed
-        if: steps.changed-files-specific.outputs.any_changed == 'true'
-        run: |
-          echo "Oops! Looks like you modified some files in dist/. Please remove them from your PR, thanks!"
-          exit 1
-
-      - name: Fail if yarn lock exists
-        if: steps.check_files.outputs.files_exists == 'true'
-        run: |
-          echo "Oops! Looks like you checked in a yarn.lock file, we use npm and package-lock.json. Please remove it from your PR, thanks!"
-          exit 1
+name: Bad files check
+on:
+  pull_request:
+
+jobs:
+  check:
+    name: Dist check
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out Git repository
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+
+
+      - name: Get specific changed files in dist
+        id: changed-files-specific
+        uses: tj-actions/changed-files@v17.3
+        with:
+          files: |
+            dist
+
+      - name: Check file existence
+        id: check_files
+        uses: andstor/file-existence-action@v1
+        with:
+          files: "yarn.lock"
+
+      - name: Fail if dist files changed
+        if: steps.changed-files-specific.outputs.any_changed == 'true'
+        run: |
+          echo "Oops! Looks like you modified some files in dist/. Please remove them from your PR, thanks!"
+          exit 1
+
+      - name: Fail if yarn lock exists
+        if: steps.check_files.outputs.files_exists == 'true'
+        run: |
+          echo "Oops! Looks like you checked in a yarn.lock file, we use npm and package-lock.json. Please remove it from your PR, thanks!"
+          exit 1

package/.github/workflows/lint-and-test.yml

@@ -1,31 +1,31 @@
-name: Lint and build
-on:
-  # Trigger the workflow on push or pull request,
-  # but only for the main branch
-  push:
-    branches:
-      - main
-      - master
-  pull_request:
-
-jobs:
-  linting:
-    name: Linting
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out Git repository
-        uses: actions/checkout@v2
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v1
-        with:
-          node-version: 14
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Lint
-        run: npm run lint
-
-      - name: Build
+name: Lint and build
+on:
+  # Trigger the workflow on push or pull request,
+  # but only for the main branch
+  push:
+    branches:
+      - main
+      - master
+  pull_request:
+
+jobs:
+  linting:
+    name: Linting
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out Git repository
+        uses: actions/checkout@v2
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: 14
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Build
         run: npm run build

package/CODE_OF_CONDUCT.md

@@ -1,46 +1,46 @@
-# 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, gender identity and expression, level of experience, 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
-
-The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+# 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, gender identity and expression, level of experience, 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
+
+The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

package/CONTRIBUTING.md

@@ -1,22 +1,22 @@
-## Getting Help
-If you need help with any Tabulator features, please ask a question on [Stack Overflow](https://stackoverflow.com/questions/tagged/tabulator)
-
-Further help resources can be found in the [Community Help Guide](http://tabulator.info/community#help) and the [Documentation Section](http://tabulator.info/) of the Tabulator website
-
-**QUESTIONS MUST NOT BE ASKED IN THE ISSUE TRACKER, IT IS FOR BUG REPORTS AND FEATURE REQUESTS ONLY**
-
-## Reporting A Bug
-Please read the [Bug Reporting Guide](http://tabulator.info/community#bug) before creating any Bug Report issues on this repo.
-
-**BUG REPORTS WILL NOT BE ACCEPTED WITHOUT A [JS Fiddle](https://jsfiddle.net/) or [Codepen](https://codepen.io/) TO DEMONSTRATE THE ISSUE**
-
-
-## Requesting A New Feature
-Please read the [Feature Request Guide](http://tabulator.info/community#feature) before creating any Feature Request issues on this repo.
-
-## Contributing To Tabulator
-There are many ways that you can contribute to Tabulator. Checkout the [Community Contribution Guide](http://tabulator.info/community#contribute) to find out how you can start contributing
-
-
-## Pull Requests
-If you are interested in contributing code to the Tabulator repo, please read the [Pull Request Guide](http://tabulator.info/community#pullrequest) before submitting your first PR
+## Getting Help
+If you need help with any Tabulator features, please ask a question on [Stack Overflow](https://stackoverflow.com/questions/tagged/tabulator)
+
+Further help resources can be found in the [Community Help Guide](http://tabulator.info/community#help) and the [Documentation Section](http://tabulator.info/) of the Tabulator website
+
+**QUESTIONS MUST NOT BE ASKED IN THE ISSUE TRACKER, IT IS FOR BUG REPORTS AND FEATURE REQUESTS ONLY**
+
+## Reporting A Bug
+Please read the [Bug Reporting Guide](http://tabulator.info/community#bug) before creating any Bug Report issues on this repo.
+
+**BUG REPORTS WILL NOT BE ACCEPTED WITHOUT A [JS Fiddle](https://jsfiddle.net/) or [Codepen](https://codepen.io/) TO DEMONSTRATE THE ISSUE**
+
+
+## Requesting A New Feature
+Please read the [Feature Request Guide](http://tabulator.info/community#feature) before creating any Feature Request issues on this repo.
+
+## Contributing To Tabulator
+There are many ways that you can contribute to Tabulator. Checkout the [Community Contribution Guide](http://tabulator.info/community#contribute) to find out how you can start contributing
+
+
+## Pull Requests
+If you are interested in contributing code to the Tabulator repo, please read the [Pull Request Guide](http://tabulator.info/community#pullrequest) before submitting your first PR

package/LICENSE

@@ -1,21 +1,21 @@
-The MIT License (MIT)
-
-Copyright (c) 2015-2022 Oli Folkerd
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+The MIT License (MIT)
+
+Copyright (c) 2015-2022 Oli Folkerd
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.