You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow up to #3133 and #6583 in which we renamed our custom Text and Button components to ExpensifyText and ExpensifyButton and added a rule to our ESLint configuration that throws an error if Text, Button or TextInput are imported from react-native.
We prefer for our custom components to be used rather than the default react native Text, Button or TextInput components, because they are built with our style/specifications already. However we have ~15 cases in our code currently where the react native components are used.
Some of those cases are in the custom components themselves, which are built atop the react native components. But we also have some cases where the react native components are being used in other components. We should see if those can be refactored to use our components instead.
The text was updated successfully, but these errors were encountered:
This is a follow up to #3133 and #6583 in which we renamed our custom
Text
andButton
components toExpensifyText
andExpensifyButton
and added a rule to our ESLint configuration that throws an error ifText
,Button
orTextInput
are imported fromreact-native
.We prefer for our custom components to be used rather than the default react native
Text
,Button
orTextInput
components, because they are built with our style/specifications already. However we have ~15 cases in our code currently where the react native components are used.Some of those cases are in the custom components themselves, which are built atop the react native components. But we also have some cases where the react native components are being used in other components. We should see if those can be refactored to use our components instead.
The text was updated successfully, but these errors were encountered: