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 shadow.class.js #2568

Merged
merged 4 commits into from
Nov 13, 2015
Merged

Update shadow.class.js #2568

merged 4 commits into from
Nov 13, 2015

Conversation

asturur
Copy link
Member

@asturur asturur commented Oct 21, 2015

add affectStroke to toObject.

@kangax do you think that we should modify also _toString method?

we need test for this, before you say that :)

closes #2566

@@ -162,6 +163,9 @@
if (this.offsetY !== proto.offsetY) {
obj.offsetY = this.offsetY;
}
if (this.affectStroke !== proto.affectStroke) {
obj.affectStroke = this.affectStroke;
}
return obj;
Copy link
Member

Choose a reason for hiding this comment

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

I think it's time to replace it with this :)

['color', 'blur', 'offsetX', 'offsetY', 'affectStroke'].forEach(function(prop) {
  if (this[prop] !== proto[prop]) {
    obj[prop] = this[prop];
  }
}, this);

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 do not understand why just this class has this feature.

Copy link
Member

Choose a reason for hiding this comment

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

That's a very good question! What happens if we remove this chunk completely?

Copy link
Member Author

Choose a reason for hiding this comment

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

That we have to remove some tests as well, and that we have to wait for 2.0 i think.
I would merge it and make a checklist for 2.0 to remove some old things.

@kangax
Copy link
Member

kangax commented Oct 21, 2015

@asturur actually let's wait with this until we merge promises branch; otherwise we'll have tons of conflicts

@asturur
Copy link
Member Author

asturur commented Oct 21, 2015

Basically promises will conflict with any open PR.
I would add them anyway, just i have to retype all when you will merge.
Let's make a label "approved" that you stick on open PR that cannot be merged soon.
So when there is to do some retyping to solve conflicts i know i'm doing on the final version of code.

What do you think?

@kangax
Copy link
Member

kangax commented Oct 21, 2015

Good idea, please add that label to this one!

On Wed, Oct 21, 2015 at 7:24 AM, Andrea Bogazzi [email protected]
wrote:

Basically promises will conflict with any open PR.
I would add them anyway, just i have to retype all when you will merge.
Let's make a label "approved" that you stick on open PR that cannot be
merged soon.
So when there is to do some retyping to solve conflicts i know i'm doing
on the final version of code.

What do you think?


Reply to this email directly or view it on GitHub
#2568 (comment).

@asturur
Copy link
Member Author

asturur commented Oct 21, 2015

I think you are the only one that can create labels.

@kangax
Copy link
Member

kangax commented Oct 21, 2015

Hm, you don't have "New label" button here? https://github.com/kangax/fabric.js/labels

@asturur
Copy link
Member Author

asturur commented Nov 12, 2015

@kangax merge this for 1.6.0 release

kangax added a commit that referenced this pull request Nov 13, 2015
@kangax kangax merged commit ae1ee00 into fabricjs:master Nov 13, 2015
@asturur asturur deleted the fix-shadow branch November 16, 2015 00:23
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.

Stroke shadow is lost when cloned
2 participants