-
-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
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
Merge release 3.4.3 into 3.5.x #385
Merged
Merged
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
Doctrine fixtures can be loaded from any directory/file (https://www.doctrine-project.org/projects/doctrine-data-fixtures/en/latest/how-to/loading-fixtures.html#loading-fixtures). But it is not clear on how to do this with the DoctrineBundle: 1. "How to Override Symfony's default Directory Structure" - https://symfony.com/doc/current/configuration/override_dir_structure.html - no word of fixtures 2. "How to Override any Part of a Bundle" - https://symfony.com/doc/current/bundles/override.html - no mentions of directories/fixtures 3. "DoctrineFixturesBundle" (this repository) - https://symfony.com/bundles/DoctrineFixturesBundle/current/index.html - no option/configuration mentioned to customize the "DataFixtures"-directory.
Co-authored-by: Claudio Zizza <859964+SenseException@users.noreply.github.com>
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
Documenting how fixtures can be moved from /src/DataFixures to a custom directory
chore: add ci tests for php 8.2
…cov-v3 chore: migrate github action for codecov-actions v1 => v3
Add return void annotation to silence deprecation msg
Add `return void` annotation to silence deprecation msg
s/DoctrineBundle/DoctrineFixturesBundle
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release Notes for 3.4.3
3.4.x bugfix release (patch)
3.4.3
CI
Improvement
return void
annotation to silence deprecation msg thanks to @PhilETaylorDocumentation