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

chore: separate create invoice screen from receive #224

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

im-adithya
Copy link
Member

Description

  • This makes Receive screen similar to Send, so now Create Invoice screen is separated
  • Also changed Receive screen to be similar to the extension when lightning address is not set, rather than leaving blank
  • Removed notifications because it feels abrupt when someone goes to Receive screen to create an invoice and see a Success page of the last received transaction

Screenshots

import { errorToast } from "~/lib/errorToast";
import { useAppStore } from "~/lib/state/appStore";

export function CreateInvoice() {
Copy link
Contributor

Choose a reason for hiding this comment

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

This page does more than just creating an invoice, is there a better name for it?

@@ -77,92 +35,11 @@ export function Receive() {
});
}

// TODO: move this somewhere else to have app-wide notifications of incoming payments
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can address this to show a toast whenever we get a payment? because received payments via lightning address will not show any more - we are removing a feature here.

Copy link
Member Author

Choose a reason for hiding this comment

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

Then we can make this provider which keeps pushing notifications via toast in-app (everywhere, not just receive), will add a commit

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