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

Fixed bug where component behaviors could be double-attached #16663

Merged
merged 1 commit into from Aug 27, 2018

Conversation

brandonkelly
Copy link
Contributor

This fixes a 3.0 bug introduced in #16430.

If a component's behaviors() method returns any behaviors without a name, then cloning it would result in the behavior getting attached twice.

Q A
Is bugfix? yes
New feature? no
Breaks BC? no
Tests pass? yes

This fixes a 3.0 bug introduced in yiisoft#16430.

If a component's behaviors() method returns any behaviors without a name, then cloning it would result in the behavior getting attached twice.
@samdark samdark merged commit 1d5ae6d into yiisoft:3.0 Aug 27, 2018
@samdark
Copy link
Member

samdark commented Aug 27, 2018

The change most probably will be lost since we've switched to https://github.com/yiisoft/yii-core etc.

@brandonkelly
Copy link
Contributor Author

@samdark Ah I had missed the new repos.

Just submitted yiisoft/yii-core#17 with the same fix.

@rob006
Copy link
Contributor

rob006 commented Aug 28, 2018

@samdark Wait, we're not going to merge changes from yii2 repo to yii-core anymore? 😱

@samdark
Copy link
Member

samdark commented Aug 28, 2018

Nope. It's unreal.

@rob006
Copy link
Contributor

rob006 commented Aug 28, 2018

It is more real than moving every change manually. Especially if you want to do this nicely, with keeping history and authorship.

@samdark
Copy link
Member

samdark commented Aug 28, 2018

There are many changes made to the code itself so commits are mostly not merge-able.

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.

None yet

3 participants