Rename ExpensiTextInput

[mateusbra]

Details

Rename component ExpensiTextInput to TextInput

Fixed Issues

$ #6760

Tests

1. Run the app and see that TextInput still working

QA Steps

1. Run the app and see that TextInput still working

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

[mateusbra]

We had a lint error due to having two style names that are the same:
textInput and textInput(expensiTextInput previously).
How you think we should rename it?

[parasharrajat]

you can try baseTextInput if that works.

[puneetlath]

It looks like we previously did it as RNText here:

App/src/components/ExpensifyText.js

Line 5 in d28716a

import {Text as RNText} from 'react-native';

So maybe that's a good format to follow for when we import these components from React Native?

[mateusbra]

It looks like we previously did it as RNText here:

App/src/components/ExpensifyText.js

Line 5 in d28716a

import {Text as RNText} from 'react-native';

So maybe that's a good format to follow for when we import these components from React Native?

You're saying we should change these imports:

App/src/components/ExpensiTextInput/BaseExpensiTextInput.js

Lines 3 to 5 in d28716a

	import {
	Animated, View, TouchableWithoutFeedback, Pressable,
	} from 'react-native';

into:

import {
    Animated as AnimatedRN, 
View as ViewRN, 
TouchableWithoutFeedback as TouchableWithoutFeedbackRN, 
Pressable as PressableRN,
} from 'react-native';

Is that what you're proposing? @puneetlath

[puneetlath]

Ah perhaps I've misunderstood. Can you help me understand why we need to call the files BaseExpensiTextInput instead of just TextInput?

[mateusbra]

@puneetlath our file structure will be this:

we won't call BaseExpensiTextInput, we will call BaseTextInput

[parasharrajat]

Small changes...

[parasharrajat]

LGTM
cc: @puneetlath

[puneetlath]

@mateusbra thanks for your patience through the holidays. Everything looks good to me, but you've picked up some merge conflicts. Once you fix those I can quickly re-approve and merge. Thanks!

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by @puneetlath in version: 1.1.25-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[OSBotify]

🚀 Deployed to production by @Jag96 in version: 1.1.26-1 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅