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

Update trait to use boot<TRAIT NAME> instead of defining a static boot function. #78

Merged
merged 1 commit into from
Aug 3, 2014
Merged

Update trait to use boot<TRAIT NAME> instead of defining a static boot function. #78

merged 1 commit into from
Aug 3, 2014

Conversation

hckurniawan
Copy link

Hey Chris, this pull request is to make the trait works better with model, whereby if models define their own static boot function, the one defined in traits will not be used. By defining "trait boot" function, this will guarantee (within certain parameter) that the "trait boot" static function will always be called.

… function. This is to allow it to work better with model which also defined their own static boot
duellsy added a commit that referenced this pull request Aug 3, 2014
…t_trait

Update trait to use boot<TRAIT NAME> instead of defining a static boot function.
@duellsy duellsy merged commit c0f0d63 into VentureCraft:develop Aug 3, 2014
@duellsy
Copy link
Member

duellsy commented Aug 3, 2014

I merged this in, but then rolled back since it won't actually work with laravel <= 4.2.6
Great solution though, will use in revisionable v2 for sure

@hckurniawan
Copy link
Author

Ah too bad then. I will keep a patch file on my install then. Thanks Chris.

@paulofreitas
Copy link
Contributor

Perhaps you could provide this patch through develop branch until v2 isn't ready? Would be great! 😃

I noticed that the package didn't worked with some of my models exactly for that reason. The odd thing is that it simply doesn't work, and for that reason it was not an easy task to figure out what was happening. I think that issuing a warning on README about that would be useful regardless of releasing a patch or not. 👍

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

Successfully merging this pull request may close these issues.

3 participants