This repository has been archived by the owner on Aug 28, 2018. It is now read-only.
Load single fixture file (issue #36) #37
Open
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
…ined in khepin_yaml_fixtures.resources
… will receive one plus argument
…t was specified in the command line
…fied in command line
|
Hey, sorry for the delay it seems I missed a lot of GH notifications. Wouldn't a specific context be enough to solve your issue here? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Early implementation of requested feature Load single fixture file (issue #36). Main changes:
--fixture-fileoption with a required value: one bundle fixture file that must be defined within khepin_yaml_fixtures.resources section. If not, it will throw an \Exception().YamlLoader::loadFixturesandYamlLoader::loadFixtureFilesmay receive one extra argument (the reqiured value specified with --fixture-file option)About the exception thrown if an unknown bundle fixture file is specified: I really don't know which is your best choice for that, but in my opinion when a user write a incorrect value for --fixture-file option, the execution shouldn't countinue. And an exception seems (for me) the best choice.