liip / liip/LiipTestFixturesBundle
[Bug]: Undeclared dependency on doctrine/dbal ^3.1.0 | ^4.0.1
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 178
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
### Preconditions
I've been upgrading old project and I began suddenly getting errors
```
Error: Call to undefined method Doctrine\DBAL\Connection::createSchemaManager()
/home/www/_project_/vendor/liip/test-fixtures-bundle/src/Services/DatabaseTools/ORMDatabaseTool.php:182
```
Later I've found that newest `liip/test-fixtures-bundle 2.7.3` does not work with my current `doctrine/dbal 2.13.9` because `liip/test-fixtures-bundle` has, based on this commit https://github.com/doctrine/dbal/commit/79ee9d0fe4835a670eed2f519228c12e308854a2, undeclared dependency on `doctrine/dbal ^3.1.0 | ^4.0.1`
### Steps to reproduce
Have project with `liip/test-fixtures-bundle 2.7.3` and `doctrine/dbal 2.13.9` and run tests.
### Expected result
Composer should not allow me such combination even install. Alternatively `liip/test-fixtures-bundle` should throw exception that it needs specific version of `doctrine/dbal`.
### Actual result
`Error: Call to undefined method Doctrine\DBAL\Connection::createSchemaManager()`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the bundle's dependency declaration and inspect src/Services/DatabaseTools/ORMDatabaseTool.php around line 182. Reproduce the failure with liip/test-fixtures-bundle 2.7.3 and doctrine/dbal 2.13.9; done means the incompatible combination is rejected during installation or reports the required DBAL version clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- database
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100