test

.123trigger

@@ -0,0 +1,11 @@
+27
+
+0.45.2
+
+0.71.2
+
+0.86.2
+
+0.91.2
+0.92.2
+0.92.3

.codeclimate.yml

@@ -0,0 +1,18 @@
+checks:
+  argument-count:
+    config:
+      threshold: 5
+  method-complexity:
+    config:
+      threshold: 7
+  method-count:
+    config:
+      threshold: 25
+  method-lines:
+    config:
+      threshold: 30
+
+exclude_patterns:
+- "**/*.spec.js"
+- "**/*.spec.ts"
+- "packages/apps-config/src/api/**/*.ts"

.dockerignore

@@ -0,0 +1,3 @@
+node_modules
+build
+.git

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+[*]
+indent_style=space
+indent_size=2
+tab_width=2
+end_of_line=lf
+charset=utf-8
+trim_trailing_whitespace=true
+max_line_length=120
+insert_final_newline=true

.env-example

@@ -0,0 +1,4 @@
+# You can define all your ENV in such a file and run docker as:
+# docker run ... --env-file .env ...
+WS_URL=ws://localhost:9944
+POLKADOT_UI_SAMPLE=42

.eslintrc.cjs

@@ -0,0 +1,28 @@
+// Copyright 2017-2022 @polkadot/apps authors & contributors
+// SPDX-License-Identifier: Apache-2.0
+
+const base = require('@polkadot/dev/config/eslint.cjs');
+
+// add override for any (a metric ton of them, initial conversion)
+module.exports = {
+  ...base,
+  ignorePatterns: [
+    ...base.ignorePatterns,
+    'jest/**/*',
+    'scripts/**/*',
+    '*.cjs'
+  ],
+  parserOptions: {
+    ...base.parserOptions,
+    project: [
+      './tsconfig.eslint.json'
+    ]
+  },
+  rules: {
+    ...base.rules,
+    // needs to be switched on at some point
+    '@typescript-eslint/no-explicit-any': 'off',
+    // this seems very broken atm, false positives
+    '@typescript-eslint/unbound-method': 'off'
+  }
+};

.gitignore

@@ -0,0 +1,25 @@
+build/
+build-cjs/
+build-esm/
+coverage/
+node_modules/
+tmp/
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+.npmrc
+.yarn/*
+!.yarn/releases
+!.yarn/plugins
+.pnp.*
+cc-test-reporter
+package-lock.json
+npm-debug.log*
+tsconfig.*buildinfo
+yarn-debug.log*
+yarn-error.log*
+.idea/
+env-config.js
+NOTES.md

.mailmap

@@ -0,0 +1,3 @@
+Jaco <[email protected]>
+github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> <[email protected]>
+github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Github Actions <[email protected]>

.nvmrc

@@ -0,0 +1 @@
+12

.prettierignore

@@ -0,0 +1,6 @@
+build
+coverage
+docker
+jest
+packages
+scripts

.prettierrc.cjs

@@ -0,0 +1,4 @@
+// Copyright 2017-2022 @polkadot/apps authors & contributors
+// SPDX-License-Identifier: Apache-2.0
+
+module.exports = require('@polkadot/dev/config/prettier.cjs');

.yarnrc.yml

@@ -0,0 +1,13 @@
+enableImmutableInstalls: false
+
+enableProgressBars: false
+
+nodeLinker: node-modules
+
+plugins:
+  - path: .yarn/plugins/@yarnpkg/plugin-interactive-tools.cjs
+    spec: "@yarnpkg/plugin-interactive-tools"
+  - path: .yarn/plugins/@yarnpkg/plugin-version.cjs
+    spec: "@yarnpkg/plugin-version"
+
+yarnPath: .yarn/releases/yarn-3.2.0.cjs

BOUNTIES.md

@@ -0,0 +1,19 @@
+# Bounties
+
+From time-to-time we will add bounties for features.
+
+These are generously provided by the [Web3 Foundation](https://web3.foundation/) and as such employees of Parity or those of the W3F are ineligible for them. (This includes people being by either Party for development or community work, related or un-related to polkadot-js).
+
+The idea is that these bounties should be left open to community participation, so only if there is no outside interest for a specific issue, should those directly or indirectly paid by the W3F for work, attempt to close an issue. (in which case it will be "un-bountied")
+
+Current bounties are tracked by the [!bounty](https://github.com/polkadot-js/apps/labels/%21bounty) label.
+
+## Process
+
+Once listed, the normal [Gitcoin](https://gitcoin.co/) process kicks in. This means application, work and payment is managed by this tool. The values for bounties are determined by the size estimation done by the team.
+
+## Some small requests
+
+Please don't start work on an issue until you have been approved via the gitcoin interface. We generally love enthusiasm and code in the repo, however short-cutting the process does create some issues for the management of the bounties. We certainly don't want to be playing favorites if 2 PRs for the same issue are created at the same time. And in cases where somebody else has been approved and an unapproved PR comes in... well, it gets really murky.
+
+When making changes, please do not force push in your PRs, especially not after a review has been started. We will clone your repo and work from that, doing a simple `pull` on a force-pushed branch ends up being, well, less than simple. We squash merge all PRs, so you do not clutter up the history by using stock-standard pushes to your branch.