Skip to content

Conversation

@yceruto
Copy link
Member

@yceruto yceruto commented Dec 5, 2017

I've missed this during the update to DoctrineFixturesBundle 3.0

@phpeek
Copy link
Contributor

phpeek commented Dec 5, 2017

@yceruto I guess that my PR is no longer relevant - #724

@yceruto
Copy link
Member Author

yceruto commented Dec 5, 2017

@phpeek Oops, I don't see your PR, I should have commented on your PR instead, sorry for that.

@phpeek
Copy link
Contributor

phpeek commented Dec 5, 2017

No worries.

@yceruto
Copy link
Member Author

yceruto commented Dec 5, 2017

closing in favor of #727

@yceruto yceruto closed this Dec 5, 2017
@yceruto yceruto deleted the fixtures branch December 5, 2017 17:13
javiereguiluz added a commit that referenced this pull request Dec 11, 2017
This PR was squashed before being merged into the master branch (closes #727).

Discussion
----------

Revamped the data fixtures

After #724 and #725 I realized that our fixtures are not following the modern best practices recommended by DoctrineFixturesBundle ([explained here](https://symfony.com/doc/master/bundles/DoctrineFixturesBundle/index.html)):

* Use 1 class to load all fixtures unless you have lots of fixtures.
* Make the fixture class extend from Symfony's `Fixture` class instead of the complicated Doctrine's classes.
* Inject services in the constructor and rely on autowiring.
* etc.

Commits
-------

adb76fc Revamped the data fixtures
@phpeek phpeek mentioned this pull request Dec 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants