Handle Live Component classes in Twig templates

[officialasishkumar]

Summary

Fixes #19458.

• Adds a Twig preprocessor for Symfony Live Component addClass(...) and removeClass(...) loading directives.
• Keeps the generic extractor boundaries unchanged so this does not broaden class extraction in non-Twig files.

Test plan

• CARGO_BUILD_JOBS=1 cargo test -p tailwindcss-oxide --lib twig -- --nocapture

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 51dbc796-8016-4600-a845-6bfb385b9d50

📥 Commits

Reviewing files that changed from the base of the PR and between 749c45e and 59764f5.

📒 Files selected for processing (4)

• crates/oxide/src/extractor/mod.rs
• crates/oxide/src/extractor/pre_processors/mod.rs
• crates/oxide/src/extractor/pre_processors/twig.rs
• crates/oxide/src/scanner/mod.rs

---

Walkthrough

This PR introduces a Twig pre-processor for the TailwindCSS scanner that handles Symfony Live Components directives. The implementation detects addClass() and removeClass() directives in Twig templates, neutralizes them by replacing the entire directive span with spaces, and handles escaped characters to preserve parenthesis balancing. The pre-processor is integrated into the module system and scanner pipeline, and a test verifies it correctly extracts class names from Twig template attributes.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change—adding a Twig preprocessor to handle Live Component classes—and is directly related to the changeset.
Description check	✅ Passed	The description is related to the changeset, explaining the addition of a Twig preprocessor for Symfony Live Component directives and references the linked issue.
Linked Issues check	✅ Passed	The changes implement a Twig preprocessor that detects and processes addClass(...) and removeClass(...) directives, directly addressing the core requirement in issue #19458.
Out of Scope Changes check	✅ Passed	All changes are focused on adding Twig preprocessor support and related test coverage, staying within the scope of handling Live Component classes in Twig templates.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Confidence Score: 4/5

Safe to merge; the change is well-scoped to .twig files and does not alter any other extraction path.

The implementation is clean and tests cover the key scenarios including nested parens and multi-directive chains. One edge case: an unclosed addClass( causes the outer scan loop to exit early, silently abandoning any directives that follow it in the same file. Real templates are well-formed so this is unlikely to matter in practice, but the fix is trivial.

crates/oxide/src/extractor/pre_processors/twig.rs — the early-break path on unclosed parens is worth a second look.

_{Reviews (1): Last reviewed commit: "Handle Live Component classes in Twig te..." | Re-trigger Greptile}

[greptile-apps]

An unclosed directive like addClass(foo (no closing )) causes the outer loop to break entirely, silently skipping every subsequent addClass/removeClass directive in the same file. In practice templates are well-formed, but a more resilient approach would be to advance cursor past the unmatched directive and continue rather than aborting.

Suggested change

	if end >= content.len() {
	break;
	}
	if end >= content.len() {
	// Unclosed parenthesis — skip past the directive name and
	// keep scanning so later directives are still processed.
	cursor += directive_len;
	continue;
	}