EZWallet: improve first-impression UX and simplify builder flow - #139
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Description
statusand updating it duringmakeOneinsrc/experiments/ezwallet/EZWalletApp.svelte.Eventinput only whenmode === 'event_drop'to remove unnecessary fields for direct claim tickets inEZWalletApp.svelte.statusnear the primary actions inEZWalletApp.svelteto improve clarity.src/experiments/ezwallet/EZWalletDropApp.svelteto clarify that the page is safe to open and replace the raw buttons with consistent, styled action controls for connecting the passkey, copying the intent, or creating another ticket.Testing
npm run -s check, which reported failures due to existing Svelte/TypeScript issues elsewhere in the repo and not introduced by these EZWallet changes.Codex Task