-
Notifications
You must be signed in to change notification settings - Fork 27.4k
docs(guide/Animations): describe your change... #14900
Conversation
The documentation for $animate lists it as element, boolean, this guide was showing boolean, element. https://code.angularjs.org/1.4.9/docs/api/ng/service/$animate
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
1 similar comment
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
I signed it! |
CLAs look good, thanks! |
1 similar comment
CLAs look good, thanks! |
Changed preceding sentence to match.
@gkalpak the documentation states this: enabled([element], [enabled]); // returns true or false // changes the enabled state for all animations // returns true or false if animations are enabled for an element // changes the enabled state for an element and its children However this guide was showing it as Which is correct then? |
The documentation 😃 |
@gkalpak also the code clearly takes element then bool, so i'm confused why you don't think this PR is valid. This is my first PR to angular, so I apologize if I am missing something here, but please advise so I can help contribute more effectively in the future. From angular-animate.js
|
The PR is fine. I tweaked the commit message a bit and merged 😄 You are probably confused by the fact we don't use a "git-merge" workflow (so GitHub doesn't display the "Merged" badge). We prefer to keep a more linear history by using |
@gkalpak thanks for your patience with me and guidance here. Much appreciated! Thanks for you and your teams hard work on Angular! |
@gkalpak yes I was confused by closed vs merge as well, thanks for the clarification |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Doc update
What is the current behavior? (You can also link to an open issue here)
Incorrect doc
What is the new behavior (if this is a feature change)?
Matches $animate documentation
Does this PR introduce a breaking change?
Fixes user confusion.
Please check if the PR fulfills these requirements
Other information:
The documentation for $animate lists it as element, boolean, this guide was showing boolean, element.
https://code.angularjs.org/1.4.9/docs/api/ng/service/$animate