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

feat: add buzzpay internal app #580

Merged
merged 13 commits into from
Sep 3, 2024
Merged

feat: add buzzpay internal app #580

merged 13 commits into from
Sep 3, 2024

Conversation

rolznz
Copy link
Contributor

@rolznz rolznz commented Sep 2, 2024

This uses the app metadata to store the readonly app connection 🤯 so that you can open the same PoS from any device

I'm not sure if it should be isolated or not?

rolznz and others added 6 commits August 28, 2024 18:01
* chore: wg.Add() before go (#559)

* chore: code cleanup (#558)

* Update README.md

Add command to make the install script executable in the instructions.

* feat: add migration card in wallet screen (#555)

* feat: add migration card in wallet screen

* chore: transfer funds if channel exists

* chore: typo

* chore: improve copy

* chore: add transfer funds button

* fix: remove duplicate icon

---------

Co-authored-by: Roland Bewick <[email protected]>

* chore: run extra workflows on PR (#563)

* chore: run extra workflows on PR

* fix: pull request workflows

* build(deps): bump github.com/nbd-wtf/go-nostr from 0.34.5 to 0.34.10 (#551)

Bumps [github.com/nbd-wtf/go-nostr](https://github.com/nbd-wtf/go-nostr) from 0.34.5 to 0.34.10.
- [Commits](nbd-wtf/go-nostr@v0.34.5...v0.34.10)

---
updated-dependencies:
- dependency-name: github.com/nbd-wtf/go-nostr
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump gopkg.in/DataDog/dd-trace-go.v1 from 1.66.0 to 1.67.0 (#552)

Bumps gopkg.in/DataDog/dd-trace-go.v1 from 1.66.0 to 1.67.0.

---
updated-dependencies:
- dependency-name: gopkg.in/DataDog/dd-trace-go.v1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix: do not render 0 on withdraw onchain funds page when reserve balance is 0 (#549)

* chore: update fly default kill timeout to ensure app gracefully shuts down (#547)

* feat: app metadata

* fix(wails): parse max length in log output endpoint (#568)

* fix: alby account image and name on transaction list

* fix: vertically center transaction item content

* fix: use slashed zero on wallet balance

* chore: align app image with app name in transaction list

* fix: ensure auth with correct user if refresh token expires (#572)

* fix: do not allow editing name of Alby Account connection

* fix: change "Create Wallet" to "Create Subaccount"

* fix: subaccount copy

* chore: update friends and family app icon

* fix: update app store images (#574)

* fix: update app store images

* chore: update paper scissors hodl and zapplanner icons

* chore: update lume and habla news icons

* chore: resize and compress zapplanner and rps logos

---------

Co-authored-by: Roland Bewick <[email protected]>

* feat: add new auto channel flow that works with existing channels (#556)

* feat: add new auto channel flow that works with existing channels

* chore: remove "first" from auto channel copy

* feat: new transaction list item design

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: Matjaž Lipuš <[email protected]>
Co-authored-by: BtcPins <[email protected]>
Co-authored-by: Michael Bumann <[email protected]>
Co-authored-by: Adithya Vardhan <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@rolznz rolznz requested a review from bumi September 2, 2024 06:06
@rolznz
Copy link
Contributor Author

rolznz commented Sep 2, 2024

@bumi edit: I'm not sure about doing it this way. It's convenient but we do not really want to store the secret like this. It might be better not not save it to the metadata.

@rolznz rolznz mentioned this pull request Sep 2, 2024
4 tasks
@bumi
Copy link
Contributor

bumi commented Sep 2, 2024

I don't think we should store the secret but just use the app to create the initial link

Copy link
Contributor

@bumi bumi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great

we need to explain more here how it works and what users can expect and what they need to do.

Comment on lines 51 to 68
const createAppResponse = await request<CreateAppResponse>(
"/api/apps",
{
method: "POST",
headers: {
"Content-Type": "application/json",
},
body: JSON.stringify(createAppRequest),
}
);

if (!createAppResponse) {
throw new Error("no create app response received");
}

const app = await request<App>(
`/api/apps/${createAppResponse.pairingPublicKey}`
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can abstract this away a bit into a createApp updateApp and fetchApp function maybe.
in the future it makes it easier for such apps to be build

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done - see requests/createApp. Updating was removed from this PR, and fetching is a one-liner using SWR

Base automatically changed from feat/uncle-jim to master September 2, 2024 10:40
@rolznz
Copy link
Contributor Author

rolznz commented Sep 3, 2024

image

image

image

@rolznz rolznz merged commit 3266e64 into master Sep 3, 2024
9 checks passed
@rolznz rolznz deleted the feat/buzzpay-internal-app branch September 3, 2024 14:31
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.

2 participants