Kevin Bond
Kevin Bond
@wouterj and I have been discussing some potential changes for 2.0. This is a list of potential ideas: - [x] #37 - [ ] Rename `ProxyRepository` to `RepositoryDecorator` and mark...
`DATABASE_URL= ./run-tests` or: ``` cp phpunit.xml.dist phpunit.xml cp phpunit-dama-doctrine.xml.dist phpunit-dama-doctrine.xml ``` And add the `` inside the `` element, then just run `./run-tests`.
Based on discussion in #234 and looking at https://github.com/dmaicher/doctrine-test-bundle/pull/128. I'm thinking we could provide 2 contexts/extensions (not sure what would be appropriate): 1. `ResetDatabaseContext/Extension`: similar to the `ResetDatabase` PHPUnit trait...
[This code](https://github.com/zenstruck/foundry/blob/1515b4e96e5ea800f34baf5cb71422ecf32dd912/src/Bundle/Maker/MakeFactory.php#L194) needs to be updated to work with MongoDB. Requires #153.
If factory exists, instantiate, if not, ask user to create.
I have never used Codeception so would like help from someone familiar with it to help with possible integration. This is a [naive POC](https://github.com/kbond/foundry-codeception-example) that could be a possible starting...
- header for each "type" of exception that is thrown by foundry - link to the proper type in the exception messages #### Solutions: > RuntimeException: Model Factories with dependencies...
`--all` flag to `make:factory` that generates factories that don't exist for all your entities. When using interactively, when listing registered entities, "All Missing" should be the final option.