deprecated-near-examples / counter-as Goto Github PK

It was confusing to try to deploy this example, simply because I had to create an account thats funded before being able to deploy.

When logging in, we can pass methods that will be placed into the function-call access key. Please see:
https://github.com/near-examples/guest-book/issues/508

and note that the methods that need to be passed will only be the mutable methods used by the frontend, not the view-only methods.

Dependabot encountered the following error when parsing your .dependabot/config.yml:

Automerging is not enabled for this account. You can enable it from the [account settings](https://app.dependabot.com/accounts/near-examples/settings) screen in your Dependabot dashboard.

Please update the config file to conform with Dependabot's specification using our docs and online validator.

Check links in README to make sure they all resolve and go where they're expected to go. The wallet link should go to https://wallet.testnet.near.org instead of https://wallet.nearprotocol.com

After install, running yarn start provides:

$ env-cmd -f ./neardev/dev-account.env parcel src/index.html
Error: Failed to find .env file at path: ./neardev/dev-account.env
    at getEnvFile (/Users/near/near-counter/node_modules/env-cmd/dist/get-env-vars.js:40:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

There wasn't anything in the README or code that sets up access keys to be able to trigger the UI. I was fully logged in with near cli, and figured the demo would create access keys on contract deploy or something.

Instead I got error:
Uncaught (in promise) Error: Wrong AccessKey used for transaction: transaction is sent to receiver_id=counter-v1.t.testnet, but is signed with function call access key that restricted to only use with receiver_id=dev-1605336831087-7847226. Either change receiver_id in your transaction or switch to use a FullAccessKey.

when I run yarn deploy, met error Command "deploy:pages" not found. in the last step,

It is very old.

Issue Description:

1. "yarn dev" command is not discussed in README.md file .I think it's better to add a "For Development" section in READEME.md, before "login" section, where we have described "yarn dev" command .

2. We should rename the "login" section to "Staging", because this section can be used for staging environment .