Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing bigInt not supported in production & better keyring initialization #227

Merged
merged 2 commits into from
Jan 26, 2022

Conversation

jimmychu0807
Copy link
Contributor

@jimmychu0807 jimmychu0807 commented Jan 26, 2022

  • Supporting bigInt issue in production and reading rpc query parameter correctly
  • Fixing issue when React strict mode is enabled, and better logic for keyring initialization

close #219

@jimmychu0807 jimmychu0807 merged commit 184b761 into main Jan 26, 2022
@jimmychu0807 jimmychu0807 deleted the jc/dev branch January 26, 2022 06:10
@jimmychu0807 jimmychu0807 changed the title Fixing Fixing bigInt not supported in production & better keyring initialization Jan 26, 2022
jimmychu0807 added a commit that referenced this pull request Mar 5, 2022
* Update polkadot-js url's (#220)

* Select from available addreses dropdown (#222)

* select from available addreses dropdown

* fix linter

* Fix console warning (#224)

* select from available addreses dropdown

* fix linter

* Fix console warning message

Co-authored-by: marlowl <marlowlieshout@hotmail.com>

* Multiple fixes (`monthly-2022-01` tag) (#225)

* Remove the traces on custom type and update to based on Node v16

* webpack 5 migration

* Rm eslint related dev-dependencies & use URLSearchParams over querystring

* Updated to the latest polkadot-js libs

* Integrate with prettier

* Friendlier connection failure message.

* Refactored current selected account into SubstrateContext

* bugfix

* Fix console warning

* Update README

* Update to solve a yarn berry issue

* Updating for CI (#226)

* Fixing  (#227)

* Supporting bigInt in production and reading rpc query parameter correctly

* Fixing issue when React strict mode is enabled, and better logic for keyring initialization

* Updating README (#228)

* Fixing issue when there is no accounts can be selected (#230)

* Fixing issue when there is no accounts can be selected

* prettier

* Fix to support polkadot-js extension (#231)

* Dynamically check if connecting chain is in dev mode (#232)

* Minor update (#233)

* update all deps (#238)

* TxButton enhancement & general packages maintenance (#239)

* dev (wip)

* Using prettier and added eslint for project

* Using the latest package without changing package.json

* eslint:write & prettier:write

Co-authored-by: Stéphane P <n3wborn@protonmail.com>
Co-authored-by: marlowl <30845815+marlowl@users.noreply.github.com>
Co-authored-by: marlowl <marlowlieshout@hotmail.com>
Co-authored-by: Dan Shields <35669742+NukeManDan@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error: Keyring should be initialised via 'loadAll' before use
1 participant