fix(ios): line break mode property added for iOS

[shubhamguptadream11]

Summary:

Solves this issue: #44107

Changelog:

[IOS] [ADDED] - Line break mode for TextInput components

Test Plan:

• Test it does not affect existing text components when set default(none) strategy.
• Tested all the modes: 'wordWrapping' | 'char' | 'clip' | 'head' | 'middle' | 'tail'.
• Tested it wouldn't affect TextInput if not provided lineBreakMode.
• Written test case with these props.

[react-native-bot]

	Fails
🚫	📋 Verify Changelog Format - See Changelog format

Generated by 🚫 dangerJS against 4609727

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	21,354,842	-14
android	hermes	armeabi-v7a	n/a	--
android	hermes	x86	n/a	--
android	hermes	x86_64	n/a	--
android	jsc	arm64-v8a	24,549,976	-15
android	jsc	armeabi-v7a	n/a	--
android	jsc	x86	n/a	--
android	jsc	x86_64	n/a	--

Base commit: fcd526d
Branch: main

[shubhamguptadream11]

@cortinico @cipolleschi
I understand the current focus is on New Architecture specific bugs. This fixes the issue coming in old and new arch both. Whenever you have some time, I would really appreciate it if you could review this PR. No rush at all—please review it whenever it's convenient for you. Thanks again!

[ecreeth]

Why not lineBreakMode?

[shubhamguptadream11]

@ecreeth This is iOS specific props. I followed convention from existing props: lineBreakStrategyIOS

[ecreeth]

@ecreeth This is iOS specific props. I followed convention from existing props: lineBreakStrategyIOS

I know, the think is that there's other props without this IOS suffix that are platform specific like: dynamicTypeRamp , minimumFontScale etc.

[shubhamguptadream11]

I thought this makes much more sense by specifying platform in props. But I am okay to rename it.

[shubhamguptadream11]

@cipolleschi @NickGerleman Can you guys please check this PR once?

[cortinico]

@cipolleschi @NickGerleman Can you guys please check this PR once?

As I already mentioned, we're hyperfocused on New Architecture-only bug at the moment so we can't review PRs within a couple of days especially if they're not New Architecture bugfixes.

[cipolleschi]

Hi @shubhamguptadream11, thanks for working on this.
This PR is too big, it will be quite hard to review and land it.

Can I suggest to split it in multiple parts?
Ideally, we can have:

1. a part that introduce the C++ changes and new functions we need
2. a part that updates the iOS part to consume those new functions, even though they are not usable from JS
3. the last part which implement the Js APIs to use the new mode.

[shubhamguptadream11]

Hi @cipolleschi ,

Thanks for the feedback! I completely understand the concern. I'll split the PR into the suggested parts:

• C++ changes and new functions
• iOS updates to consume those new functions (without JS integration)
• Implementation of the JS APIs for the new mode
  I'll work on breaking it down and submit the smaller, more manageable PR's shortly.

Thanks again for the guidance!

[shubhamguptadream11]

Hi @cipolleschi

I've gone ahead and split the original PR into three separate ones as suggested:

[PR 1] - Introduces the C++ changes and new functions.
[PR 2] - Updates the iOS part to consume the new functions (not yet exposed to JS).
[PR 3] - Implements the JS APIs for the new mode.
Each PR is focused on a specific part of the overall change, making them easier to review and land. Please feel free to review them at your convenience.