Fixes for animate docs

[FRSgit]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Updated animaton-aware directive tables both on ngAnimate's module and on animate guide pages.

What is the current behavior? (You can also link to an open issue here)
That's an effect of discussion which took place under #16561

What is the new behavior (if this is a feature change)?
No, just docs.

Does this PR introduce a breaking change?
No.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Fix/Feature: Docs have been added/updated
• Fix/Feature: Tests have been added; existing tests pass

Other information:

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). 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 (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). 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 (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[FRSgit]

I signed it!

[googlebot]

CLAs look good, thanks!

[googlebot]

CLAs look good, thanks!

[gkalpak]

LGTM except for the (re-)ordering. My guess is that you tried to switch to some sort of alphabetic ordering, but it doesn't seem to have worked out very well 😛

[FRSgit]

Yup, I've reordered it, so they appear in the same order as in navigation of the docs, what's bad about it? (So, it's sorted by module names, then by component names).
Did the previous order have any sense at all? It wasn't done by type (modules/directives), not by name, even parts of the same modules wasn't always near each other (like ngMessages & ngMessage).

[gkalpak]

Yup, I've reordered it, so they appear in the same order as in navigation of the docs, what's bad about it? (So, it's sorted by module names, then by component names).

Oh, I see. This is not at all obvious to the reader (especially since module names are not shown in the table.

Did the previous order have any sense at all?

Previously, they were grouped by animation type (e.g. structural vs non-structural), but not ordered other than that (afaict). Also, similar directives where close to each other (e.g. ngHide/ngShow).

Please either order alphabetically by directive name (either ungrouped or grouped by animation type) or leave previous order.

[FRSgit]

Previously, they were grouped by animation type (e.g. structural vs non-structural), but not ordered other than that (afaict). Also, similar directives where close to each other (e.g. ngHide/ngShow).

Ah, I get it now. Well, then I'll put them alphabetically since it's the only obvious (for reader) way of handling it I guess (the structural naming is not so openly described in docs).
Still, the main focus there was to sync table from naAnimate page & animation guide.

[FRSgit]

Tables reordered & unified.

[gkalpak]

LGTM (with one minor suggestion) 👍

[gkalpak]

The text of the link will API docs (which is kind of vague). Maybe change it to `$animate` API docs?

[FRSgit]

Sure, just copied & pasted it from animations guide, wait for the commit ⌛️

[FRSgit]

Done!