Skip to content

Changes reflecting deprecated methods: Issue Ticket 665 #669

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

Closed
wants to merge 3 commits into from

Conversation

citygent
Copy link
Contributor

New pull request, had some issues before with CLA and resetting author.

@jquerybot
Copy link

Thank you for your pull request. It looks like this may be your first contribution to a jQuery Foundation project, if so we need you to sign our Contributor License Agreement (CLA).

📝 Please visit http://contribute.jquery.org/CLA/ to sign.

After you signed, the PR is checked again automatically after a minute. If there's still an issue, please reply here to let us know.


If you've already signed our CLA, it's possible your git author information doesn't match your CLA signature (both your name and email have to match), for more information, check the status of your CLA check.

@citygent
Copy link
Contributor Author

Cripes, I definitely have the same details in git config and the CLA signature!

Can someone please look into this for me and confirm I do. I resubmitted CLA form and globally changed my git config to match before even forking the second time, so at a loss to this CLA Fail.

@kborchers
Copy link
Member

@citygent I don't see a signature with your name nor email or any combination of them in our signature list. If you click the details link next to the error it tells you exactly what name and email it expects to find in the list based on the info used to commit the change.

@citygent
Copy link
Contributor Author

screen shot 2015-09-25 at 19 04 54

Hi @kborchers

Do you mean this? Top and bottom match :)

@kborchers
Copy link
Member

Right, they match because that is where the checker got that information but that information is not in the signature database. My guess is if you sign the CLA with that information this check will turn green.

@citygent
Copy link
Contributor Author

Not sure why this seems to have fixed itself. Maybe I was expecting the CLA check to update quicker than it does. Apologies!

```

**Note:** A note about the `dataType` setting: if the server sends back data that is in a different format than you specify, your code may fail, and the reason will not always be clear, because the HTTP response code will not show an error. When working with Ajax requests, make sure your server is sending back the data type you're asking for, and verify that the `Content-type` header is accurate for the data type. For example, for JSON data, the `Content-type` header should be `application/json`.

**Deprecation:** Deprecation Notice: The jqXHR.done(), jqXHR.fail(), and jqXHR.always() callbacks are used above, but you may see the older jqXHR.success(), jqXHR.error(), and jqXHR.complete() callbacks, and should update the code accordingly: As of jQuery 1.8 these are deprecated and will eventually be removed.
Copy link
Member

Choose a reason for hiding this comment

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

This is more something for API docs IMHO. Keep in mind that most people are here to learn and use api.jquery.com as a reference. I feel like we shouldn't bother them with deprecated stuff they should be aware of just yet.

@citygent
Copy link
Contributor Author

citygent commented Nov 9, 2015

Apologies it has taken so long to address your notes, @arthurvr

@AurelioDeRosa
Copy link
Member

LGTM 👍

kswedberg pushed a commit to kswedberg/learn.jquery.com that referenced this pull request Mar 13, 2016
Krinkle pushed a commit that referenced this pull request Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants