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(EMI-2095): Add Swipeable component #263

Closed
wants to merge 1 commit into from

Conversation

MrSltun
Copy link
Member

@MrSltun MrSltun commented Oct 1, 2024

This PR resolves EMI-2095

Description

This PR adds a Swipeable component Palette using react-native-gesture-handler swipeable

Demo

Android iOS
swipeable-android.mov
swipeable-ios.mov

@MrSltun MrSltun self-assigned this Oct 1, 2024
@artsy-peril artsy-peril bot added Jira Synced Indicates that Peril has connected this PR to Jira Version: Minor A deploy for new features labels Oct 1, 2024
export interface SwipeableProps {
children: React.ReactNode
actionOnPress: () => void
actionCompoent: React.ReactNode
Copy link
Contributor

Choose a reason for hiding this comment

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

actionComponent

Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure if we should leave it so flexible to be any kind of element, that's why I recommend going through DS first

@araujobarret
Copy link
Contributor

araujobarret commented Oct 1, 2024

The code looks fine, and simple to use however I feel like this component should be somehow in DS first, that's the common blackhole of Eigen's UI elements, they exist in product mockups but never in DS, once you search for the source of truth no one can find it.
@MrSltun , could you please align with your team to add this element to the DS first? For example the action element we use might be something totally different than we support right now.

Copy link
Member

@gkartalis gkartalis left a comment

Choose a reason for hiding this comment

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

Looking good on my side, left only a versioning question

@@ -44,6 +44,7 @@
"react-native-blurhash": "^1.1.11",
"react-native-collapsible-tab-view": "^8.0.0",
"react-native-fast-image": "^8.6.3",
"react-native-gesture-handler": "2.19.0",
Copy link
Member

Choose a reason for hiding this comment

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

**question: ** Since we are introducing react-native-gesture-handler in palette why didn't we go for the latest version?

Noticed on the docs that there is this requirements table depending on the react native version that we might need to consult when picking the right version

Copy link
Member Author

@MrSltun MrSltun Feb 18, 2025

Choose a reason for hiding this comment

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

Good idea! But I have to say that this is PR is not active since we decided to add the Swipeable in Eigen instead (artsy/eigen#10879) 😅 my bad for not keeping track of this one, I'll close it since probably won't add the swipeable to palette anytime soon, but will reopen it once we get back to it :)

Copy link
Member

Choose a reason for hiding this comment

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

ooh okay no worries then

@MrSltun
Copy link
Member Author

MrSltun commented Feb 18, 2025

closing this in favor of artsy/eigen#10879

@MrSltun MrSltun closed this Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Jira Synced Indicates that Peril has connected this PR to Jira Version: Minor A deploy for new features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants