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: #163: pair selector #204

Merged
merged 15 commits into from
Dec 19, 2024
Merged

feat: #163: pair selector #204

merged 15 commits into from
Dec 19, 2024

Conversation

VanishMax
Copy link
Contributor

@VanishMax VanishMax commented Dec 11, 2024

Closes #163

Rewamped pair selector with:

  • Starring feature
  • Displaying pairs from backend with volume represented in USDC
  • Searching pairs by symbol and by name
  • Saving recent searches
  • Loading and error states
pair-selector.mp4

@VanishMax VanishMax self-assigned this Dec 11, 2024
@VanishMax VanishMax requested a review from a team December 18, 2024 12:43
@VanishMax VanishMax marked this pull request as ready for review December 18, 2024 12:43
Copy link
Contributor

@grod220 grod220 left a comment

Choose a reason for hiding this comment

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

High quality work! Design-wise, a few more comments. Will let you make the call on these:

  • The Clear button should have the frosted-glass background. Think there is a css filter for this.
Screenshot 2024-12-18 at 5 32 59 PM
  • After clicking Clear the text remains in the input field.
  • The loading skeleton is missing some detail:
Screenshot 2024-12-18 at 5 35 13 PM
  • Missing the "No results" design (let's make sure we have the error state too):
Screenshot 2024-12-18 at 5 36 12 PM
  • We seem to be missing the "confirm" state. Is it because you felt it unnecessary?
Screenshot 2024-12-18 at 5 37 37 PM
  • Question: would it be possible to pre-fetch the state before the user clicks on the component? That way, there really isn't a "loading" state the majority of users encounter.

Comment on lines +28 to +32
JSON.stringify(
pairs.map(pair => ({
base: pair.base.toJson(),
quote: pair.quote.toJson(),
})),
Copy link
Contributor

Choose a reason for hiding this comment

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

question: would it be easier if we just stored symbol pairs versus the whole metadata objects?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this would delay showing data to user. Idk, for me it's more complicated to calculate the Metadata from symbol than storing it like this

Comment on lines 10 to 12
if (typeof window !== 'undefined') {
this.setup();
}
Copy link
Contributor

Choose a reason for hiding this comment

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

possible issue: see connectionStore.setup() in the App component. This was added because this pattern produced hydration errors in the connect store. This may need to go likewise in that useEffect (?).

Comment on lines 13 to 15
if (typeof window !== 'undefined') {
this.setup();
}
Copy link
Contributor

Choose a reason for hiding this comment

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

same comment as the other

@VanishMax
Copy link
Contributor Author

VanishMax commented Dec 19, 2024

Addressed all PR feedback. The UI/UX is now the same as it is supposed to be in Figma. Fixed the mobile screens too

@VanishMax VanishMax merged commit 8aad7da into main Dec 19, 2024
3 checks passed
@VanishMax VanishMax deleted the feat/#163-asset-selector branch December 19, 2024 12:36
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.

Updated asset selector component
2 participants