-
Notifications
You must be signed in to change notification settings - Fork 2
feat: adding callback server for peer-to-peer example #18
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
Conversation
|
| metadata: { | ||
| description: 'From peer-to-peer example script' |
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.
examples/peer-to-peer/index.js
Outdated
| return new Promise((resolve) => { | ||
| let server | ||
| const app = express() | ||
| app.use(express.json()) |
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.
Don't need this.
| app.use(express.json()) |
ce5549b to
5c844e4
Compare

Changes proposed in this pull request
peer-to-peerapp exampleContext
During hackathons, when participants used the
peer-to-peerexample app, after going through authorization at the test wallet, they would be redirect to a not so nice 202 "Accepted" page screen. Now, thepeer-to-peerexample includes a callback server for handling the finish redirect. IMO its a cleaner experience and also the script now demonstrates how they can use the finish in their own application.Before:

After: