Skip to content

Skip base test_data.yaml fixture when Doctrine Migrations already imported it #42

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.

Sign up for GitHub

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

Closed
Steveb-p wants to merge 1 commit into from
Closed

Skip base test_data.yaml fixture when Doctrine Migrations already imported it #42

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/contracts/IbexaTestKernel.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,10 +123,21 @@ public function getSchemaFiles(): iterable
}

/**
* When the Doctrine Migrations schema-install path is active (as opposed to the legacy,
* event-driven SchemaBuilderEvent path), core's own ImportDataMigration already inserts this
* same baseline content as part of schema install -- importing it again here would violate
* unique constraints. Package-specific fixtures added by subclasses (via
* `yield from parent::getFixtures(); yield new Fixture(...)`) are unaffected and still run in
* both modes, since they're additive rather than overlapping with ImportDataMigration's output.
*
* @return iterable<\Ibexa\Contracts\Core\Test\Persistence\Fixture>
*/
public function getFixtures(): iterable
{
if (getenv('IBEXA_TEST_SCHEMA_BUILDER_EVENT_ENABLED') === '0') {
return;
}

yield from (new DefaultFixtureProvider())->getFixtures();
}

Expand Down
Loading