Skip to content

Fix: multiple translations inside an array#83

Merged
erikyo merged 2 commits intomasterfrom
array-parsing
Feb 14, 2026
Merged

Fix: multiple translations inside an array#83
erikyo merged 2 commits intomasterfrom
array-parsing

Conversation

@erikyo
Copy link
Collaborator

@erikyo erikyo commented Feb 13, 2026

Refactor argument handling for translation functions, should allow multiple translations inside an array

@erikyo erikyo requested a review from johnhooks February 13, 2026 09:47
@erikyo
Copy link
Collaborator Author

erikyo commented Feb 13, 2026

@johnhooks what do you think about? It's a lot of code, but in some cases (e.g., in PHP [__(“a”),__(‘b’),__(“c”)] it's necessary (or at least it's the only way I've found).

@johnhooks
Copy link
Contributor

@erikyo your solution looks correct to me. The fix doesn't assume the structure of the call expression arguments.

:shipit:

@erikyo erikyo merged commit 13d7dc8 into master Feb 14, 2026
3 checks passed
@erikyo
Copy link
Collaborator Author

erikyo commented Feb 15, 2026

@johnhooks Thank you! I was a bit unsure because I didn't want to burden doTree fixing edge cases...

As usual, you are very kind and thorough. 🍻

@erikyo erikyo deleted the array-parsing branch February 15, 2026 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants