Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

docs(orderBy): clarify behavior of default comparator #15302

Closed
wants to merge 1 commit into from

Conversation

arw-travela
Copy link
Contributor

Doc update to clarify behavior of the default comparator starting in v1.3.7. See #15293

Documentation updates to clarify default sort behavior. See
angular#15293 for more information
@googlebot
Copy link

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!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

1 similar comment
@googlebot
Copy link

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!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@arw-travela
Copy link
Contributor Author

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

1 similar comment
@googlebot
Copy link

CLAs look good, thanks!

@Narretz
Copy link
Contributor

Narretz commented Oct 20, 2016

You can update the commit message by cloning your fork of this repo, amending the commit, and then force pushing it back.

@gkalpak
Copy link
Member

gkalpak commented Oct 20, 2016

This PR is for the 1.3.x branch. This is not maintained any more and even if we merged it, it wouldn't show up in the docs until there is a new release (and there will be no new release on the 1.3.x series 😃).

@gkalpak gkalpak closed this Oct 20, 2016
@arw-travela
Copy link
Contributor Author

No problem - makes sense!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants