[9.x] Avoid matching multi-line imports in GenerateCommand stub templates #43093
Conversation
This file contains 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
Multi-line imports are broken:
```
use Illuminate\Foundation\Testing\{
DatabaseTransactions,
WithFaker,
};
```
Results in output:
```
DatabaseTransactions,
WithFaker,
use Illuminate\Foundation\Testing\{
};
```
n8man
changed the title
GrahamCampbell
changed the title
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.
Sorting of multi-line use-imports are broken in *.stub templates.
Input:
Results in output:
This regex change avoids matching multi-line use-imports. It's an improvement in that the rendered stub is no longer generating invalid php code. The downside is that sorting will not include any multi-line imports.