Add PhpLexer to support extraction from standard PHP files and Laravel Blade #1134
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implement tests for extracting single and multiple keys from translation functions. - Support for custom function names in extraction. - Handle extraction when additional parameters are present. - Test extraction from nested functions. - Validate extraction of keys with special syntax (%key and :key). - Ensure correct handling of escaped characters in strings. - Confirm that no exceptions are thrown on invalid PHP input.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why am I submitting this PR
This PR introduces a PhpLexer to support extraction of translation keys from both Laravel Blade templates and standard PHP files.
It handles common translation function calls such as
t('...'),__('...'),@lang('...'), andtrans('...').The lexer supports escaped quotes, avoids concatenated strings, and correctly processes nested translation functions.
All features are covered by unit tests to ensure compatibility with typical PHP usages.
Does it fix an existing ticket?
No