Add CI check to ensure all TextViews have a style check

[BenHenning]

Related issue: #3971. We need to make sure that TextViews have a centrally managed style set so that RTL/LTR settings can be properly managed. To do this, we need a CI check that runs a script which parses all layout files to ensure that TextView elements have a style set that corresponds to a local codebase style (i.e. uses @style/).

For reference, I suggest looking at the manifest transformation script since it parses & modifies XML today (so it's a good basis for the parsing needs of this new TextView script).

[BenHenning]

/cc @veena14cs

[yash10019coder]

@BenHenning I would like to work on this issue

[BenHenning]

@BenHenning I would like to work on this issue

Sounds good! Assigning this to you @yash10019coder.

[Rd4dev]

Unassigning myself to free it up for others. Will pick it up later if it's still available.

[manas-yu]

HI @adhiamboperes can i work on this issue, i'll add the requested TextViewStyleChecker script.

[adhiamboperes]

@manas-yu, could you please provide an outline of how you would approach this issue?

[manas-yu]

@manas-yu, could you please provide an outline of how you would approach this issue?

@adhiamboperes I'll add the TextViewStyleChecker in scripts/xml, using TransformAndroidManifest/XmlSyntaxCheck.kt as a reference. The script will verify whether TextView elements are missing the @style attribute. I'll update the BUILD.bazel file to include this new script and add corresponding tests to ensure it works as expected.

[adhiamboperes]

@manas-yu, re #5599 (comment)

I need some clarification regarding the issue. The issue states that the script should parse all layout XML (files in app/src/main/res/layout*) and ensure all TextView elements have a style set (using @style/) that aligns with the local codebase style. However, some files (mentioned in the previous comment) have TextView elements without a style attribute. Certain cases need to be considered, such as when the text is center-aligned (gravity="center"), uses hardcoded left/right attributes, or lacks direction-sensitive layout attributes. To proceed, I would need an exact set of criteria to differentiate TextView elements with a style set for RTL/LTR settings from those without. This will help ensure the script enforces the style requirement accurately without affecting valid exceptions.

• Each TextView must include a style attribute referencing a centrally managed style (e.g., @style/YourTextViewStyle).
• The centrally managed style should handle RTL/LTR settings by specifying textAlignment, gravity, and any other properties that affect directionality.
• If the TextView has gravity="center", it may not require a style explicitly managing directionality since it is inherently direction-neutral.
• Avoid enforcing the style check for elements with hardcoded left or right attributes (e.g., paddingLeft, layout_marginRight), but log these cases for potential future refactoring to use start/end attributes instead.
• TextViews with no text or direction-sensitive layout attributes (e.g., purely used for spacing or decoration) may also be valid without a style, though these should be carefully reviewed to confirm.

I would defer to @BenHenning for further clarification.