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

MigrationCreator::firePostCreateHooks not backwards compatible with current version. #24907

Closed
chrishalbert opened this issue Jul 20, 2018 · 5 comments

Comments

@chrishalbert
Copy link

chrishalbert commented Jul 20, 2018

  • Laravel Version: 5.6.28
  • PHP Version: 7.1
  • Database Driver & Version: N/A

Description:

The recent change to MigrationCreator::firePostCreateHooks() adds an additional parameter to the method signature. This method is protected, however, subclasses can still call/rely on this in earlier versions. For prior versions of 5.6, we'll see breaking changes.

Steps To Reproduce:

When I run my build on travis-ci for https://github.com/chrishalbert/laravel-nomadic project on 7.1, I see this output: https://travis-ci.org/chrishalbert/laravel-nomadic/jobs/406202387.
image

PR coming your way.

@Miguel-Serejo
Copy link

Laravel doesn't follow semver. https://laravel.com/docs/5.6/releases#versioning-scheme

@chrishalbert
Copy link
Author

True, however, according to: Minor features that are fully backwards compatible with the current Laravel release may be sent to the latest stable branch. ref: https://laravel.com/docs/5.6/contributions#which-branch, this should still be fully compatible with the rest of 5.6, which it is not.

@chrishalbert
Copy link
Author

Editing ticket description per your notes @36864

@chrishalbert chrishalbert changed the title MigrationCreator::firePostCreateHooks not following semvar updates with recent enhancement MigrationCreator::firePostCreateHooks not backwards compatible with current version. Jul 20, 2018
@chrishalbert
Copy link
Author

#24916

@chrishalbert
Copy link
Author

chrishalbert commented Jul 21, 2018

Closing this as no plans are to fix this

If anyone comes by this in their code, you can just add a default unused param as a work around:


    protected function firePostCreateHooks($table = null)
    {
        $this->fireHook($this->postCreate);
    }

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

No branches or pull requests

2 participants