We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The following demonstrates what I mean with automatic field resolving:
$this->factory ->define('Entity') ->resolve();
And that would be all you need. Of course you would have the option to override the fields that you specifically want to define.
One could read and resolve the fields from Doctrine mapping annotations.
The text was updated successfully, but these errors were encountered:
I guess the default values would be something like "example_username_%d".
"example_username_%d"
One could also add an annotation like `@example "My Example Value %d". Then the example would be close to the validation annotations.
Actually, it looks like xi-fixtures could be made entirely annotation-driven. Not sure if we want to, since code is more flexible than annotations.
Sorry, something went wrong.
I would not want to mix test and production code. Therefore I think annotations (on the actual Entity) are out of the question.
Hmm, I don't see the problem. Annotations are effectively just comments, and these could even be informative ones. An analogy could be made to types.
No branches or pull requests
The following demonstrates what I mean with automatic field resolving:
And that would be all you need. Of course you would have the option to override the fields that you specifically want to define.
How?
One could read and resolve the fields from Doctrine mapping annotations.
Downsides/blockers/to be resolved
The text was updated successfully, but these errors were encountered: