-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update sdk to 13 #23
Update sdk to 13 #23
Conversation
d2c0caa
to
906ffbe
Compare
would it be also good to migrate to vite and eventually pinia? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see following log in the console:
caught (in promise) NoWalletConnectedError: You are not connected to Wallet
at Proxy._ensureConnected (AeSdkAepp.ts:172:1)
at Proxy._ensureAccountAccess (AeSdkAepp.ts:176:1)
at Proxy._resolveAccount (AeSdkAepp.ts:73:1)
at get address (AeSdkBase.ts:131:1)
at Reflect.get (<anonymous>)
at Object.get (reactivity.esm-bundler.js:492:1)
at fetchAccountInfo (wallet.js:87:1)
at connectToNode (wallet.js:101:1)
at Proxy.onNetworkChange (wallet.js:51:1)
at updateNetwork (AeSdkAepp.ts:106:1)
can this be ignored? other than that the update looks good to me 👍
note: this is shown in the console before connecting the wallet. I am not sure if this is already a "problem" in the latest version of the boilerplate
do you really mean pinata or did you want to say pino? 🤔 |
It is not intended to be there, I'm looking for a fix |
@marc0olo pinia sorry |
I've fixed the error in a separate commit. The bug was because at the last moment before release I made sdk to call Would be really good to update this repo to vite and pinia, but this would break the integration of contract builder in #24, so I won't do it 🙃 |
No description provided.