Skip to content
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

Updating DoctrineMigrationsBundle for Doctrine Migrations 2.0 #228

Merged
merged 3 commits into from Jun 5, 2018
Merged

Conversation

jwage
Copy link
Member

@jwage jwage commented Jun 4, 2018

Closes #226

  • Upgrade to PHP 7.1
  • Upgrade to Doctrine Migrations 2.0
  • Add PHPStan
  • Add Doctrine Coding Standards
  • Add Scrutinizer
  • Update travis ci configuration to match other Doctrine projects
  • Add new commands
  • Add new configuration options
  • Update Resources/doc/index.rst

@jwage jwage force-pushed the 2.0 branch 4 times, most recently from f84b4ea to 74c6db7 Compare June 4, 2018 19:51
@jwage jwage added this to the 2.0 milestone Jun 4, 2018
@jwage jwage force-pushed the 2.0 branch 2 times, most recently from c4498b6 to e5079eb Compare June 4, 2018 20:45
@jwage jwage requested a review from stof June 4, 2018 21:00
@jwage jwage force-pushed the 2.0 branch 11 times, most recently from 8c2f5bc to 41532ba Compare June 4, 2018 22:35
@jwage jwage force-pushed the 2.0 branch 6 times, most recently from e224624 to 2f223bb Compare June 5, 2018 02:51
@jwage jwage force-pushed the 2.0 branch 2 times, most recently from 1f04ba5 to a7f650d Compare June 5, 2018 15:27
@jwage jwage force-pushed the 2.0 branch 3 times, most recently from 93f2765 to b6ac051 Compare June 5, 2018 17:56
- 7.1
- 7.2
- nightly

cache:
directories:
- $HOME/.composer/cache
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should cache only $HOME/.composer/cache/files, to avoid invalidating the Travis cache due to changes in the packagist metadata (cached in $HOME/.composer/cache/repo). Packagist changes too often (every few minutes) to avoi this invalidation.


$configuration->setMigrationsColumnName($container->getParameter('doctrine_migrations.column_name'));
$configuration->setMigrationsColumnLength($container->getParameter('doctrine_migrations.column_length'));
$configuration->setMigrationsExecutedAtColumnName($container->getParameter('doctrine_migrations.executed_at_column_name'));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these ones should check for an explicit config file, as done for the table name

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure I understand what you mean. You mean how the others have an if (empty(...)) condition around them? These values in the Configuration class have a default value so it can't work the same way unless you have another thought/idea?

"symfony/framework-bundle": "~2.7|~3.3|~4.0",
"php": "^7.1",
"symfony/framework-bundle": "~3.4|~4.0",
"doctrine/coding-standard": "^4.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be a dev requirement

"doctrine/migrations": "^1.1"
"doctrine/migrations": "^2.0@dev",
"phpstan/phpstan": "^0.9.2",
"phpstan/phpstan-strict-rules": "^0.9"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be a dev requirement

"doctrine/doctrine-bundle": "~1.0",
"doctrine/migrations": "^1.1"
"doctrine/migrations": "^2.0@dev",
"phpstan/phpstan": "^0.9.2",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be a dev requirement

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These were fixed in #229

->scalarNode('column_name')->defaultValue('version')->end()
->scalarNode('column_length')->defaultValue(255)->end()
->scalarNode('executed_at_column_name')->defaultValue('executed_at')->end()
->scalarNode('all_or_nothing')->defaultValue(false)->end()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these new settings should be added in the XSD for people using XML config files.

@jwage jwage modified the milestones: 2.0.0-beta1, 2.0 Aug 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants