-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Unify the distance rates enabled label styles with other feature row styles #39557
Merged
Merged
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
bef52de
Make sure the style for distance rates row is same as for categories …
mountiny 83dd287
Fix lint
mountiny 2252271
Create a new component for the right element
mountiny 4290391
Create a new component for the right element
mountiny be00a70
Merge branch 'main' into vit-39556
mountiny ca03fd1
Address PR feedback
mountiny File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
36 changes: 36 additions & 0 deletions
36
src/components/SelectionList/ListItemRightElementWithArrow.tsx
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
import React from 'react'; | ||
import {View} from 'react-native'; | ||
import Icon from '@components/Icon'; | ||
import * as Expensicons from '@components/Icon/Expensicons'; | ||
import Text from '@components/Text'; | ||
import useLocalize from '@hooks/useLocalize'; | ||
import useTheme from '@hooks/useTheme'; | ||
import useThemeStyles from '@hooks/useThemeStyles'; | ||
|
||
type ListItemRightElementWithArrowProps = { | ||
enabled?: boolean; | ||
}; | ||
|
||
function ListItemRightElementWithArrow({enabled}: ListItemRightElementWithArrowProps) { | ||
const styles = useThemeStyles(); | ||
const theme = useTheme(); | ||
const {translate} = useLocalize(); | ||
|
||
return ( | ||
<View style={styles.flexRow}> | ||
<Text style={[styles.alignSelfCenter, styles.textSupporting, styles.pl2, styles.label]}> | ||
{enabled ? translate('workspace.common.enabled') : translate('workspace.common.disabled')} | ||
</Text> | ||
<View style={[styles.p1, styles.pl2]}> | ||
<Icon | ||
src={Expensicons.ArrowRight} | ||
fill={theme.icon} | ||
/> | ||
</View> | ||
</View> | ||
); | ||
} | ||
|
||
ListItemRightElementWithArrow.displayName = 'ListItemRightElementWithArrow'; | ||
|
||
export default ListItemRightElementWithArrow; |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am no engineer but just noting that not all of these table rows have the enabled/disabled text, right? Sometimes they might have nothing, or sometimes they might have a badge (Owner, Admin, card limit, etc). Not sure how that might change this abstraction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shawnborton You're right that it can be a badge in other use cases. But this component will be only used by rows (of different components) to show the enabled status.
Maybe rename it to
ListItemRightElementEnabledStatus
orRightElementEnabledStatus
sounds better?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah so for this case, I have only abstracted the component used in the Categories, Tags, Taxes and Distance rates, The other usecases might have different styles or even different components inside as you mentioned.
Abstracting this more might lead to loosing the benefit in this case as we might have to pass more props and styles which would again have to be defined individually in pages/ components this is used and it could lead to different styles.
I can rename this based on @eh2077 suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, I don't feel too strongly really - mostly just noting that we have different row behaviors in various places. Thanks for hearing me out!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can certainly see us further abstracting this especially for the Badge style - Members with roles, Cards with limits etc. I think we can do that as we go though