Alexdawn/feature/list option #509
Open
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
Member
|
Listing fixtures should be a separate command instead of being an option on the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Sorry If i've missed anything this is my first contribution to a symfony project. I've tried to follow PSR and symfony style guides.
A couple of optional flags, I've needed to help run fixtures on a private project, that should be useful to anyone else trying to see a list of fixtures or debug single fixtures in a project with many many fixtures or multiple entity-managers.
--list shows all the fixtures and any dependencies, groups in a symfony table (respects both group and filter-name filters)
--filter-name allows filtering of fixtures by name in addition to group
closes my feature request #508