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

swap: make ChainSelector row fixed to top of list #6206

Conversation

greg-schrammel
Copy link
Contributor

@greg-schrammel greg-schrammel commented Oct 16, 2024

Fixes APP-####

What changed (plus any additional context for devs)

should we add some animation/separator/fade/idk to the list clipping behind this header?

Screen recordings / screenshots

Screen.Recording.2024-10-16.at.03.19.20.mov

What to test

Copy link

linear bot commented Oct 16, 2024

@brunobar79
Copy link
Member

Launch in simulator or device for 17e95ca

Copy link
Contributor

@walmat walmat left a comment

Choose a reason for hiding this comment

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

LG, but what about the token to sell list selector?

@brunobar79
Copy link
Member

Launch in simulator or device for b54aa94

@greg-schrammel greg-schrammel merged commit 61c9d54 into develop Oct 24, 2024
8 checks passed
@greg-schrammel greg-schrammel deleted the gregs/app-1514-make-chainselector-row-fixed-to-top-of-list branch October 24, 2024 15:14
greg-schrammel added a commit that referenced this pull request Oct 24, 2024
* ChainSelector row fixed to top of list

* sticky chainselector on token to sell too
Copy link

sentry-io bot commented Oct 26, 2024

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

  • ‼️ React ErrorBoundary TypeError: undefined is not a function createRainbowStore$argument_0(src/state/assets/... View Issue

Did you find this useful? React with a 👍 or 👎

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.

4 participants