Skip to content
This repository has been archived by the owner on Dec 23, 2017. It is now read-only.

jQuery 3.2.1 #1986

Merged
merged 4 commits into from
May 10, 2017
Merged

jQuery 3.2.1 #1986

merged 4 commits into from
May 10, 2017

Conversation

noahmanger
Copy link
Contributor

@noahmanger noahmanger commented Apr 26, 2017

This updates jQuery to the latest version. I clicked through the site and everything seems to be working. I also ready through the upgrade guide and checked for instances of the things they warned about and I didn't find anything concerning.

The one snag is that a single test is failing, which seems to perhaps relate to the change in the $.Deferred() implementation.

But I'm stumped, so I'd appreciate if someone else could take a look.

Update: the test issue is resolved.

@noahmanger noahmanger requested a review from ccostino May 1, 2017 21:51
@codecov-io
Copy link

codecov-io commented May 1, 2017

Codecov Report

Merging #1986 into develop will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #1986   +/-   ##
========================================
  Coverage    55.33%   55.33%           
========================================
  Files           48       48           
  Lines         3273     3273           
  Branches       384      384           
========================================
  Hits          1811     1811           
  Misses        1446     1446           
  Partials        16       16
Impacted Files Coverage Δ
static/js/modules/download.js 90.08% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9cebcdc...45d9cb4. Read the comment docs.

Copy link
Contributor

@ccostino ccostino left a comment

Choose a reason for hiding this comment

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

There's a lot to cover with the updated Deferred object API and behavior, so it makes sense to me to hold off on more changes until this upgrade is in place first, if needed. If that sounds good to you too @noahmanger then this is good to merge!

@@ -137,7 +137,7 @@ DownloadItem.prototype.refresh = function() {
contentType: 'application/json',
dataType: 'json'
});
this.promise.then(this.handleSuccess.bind(this));
this.promise.done(this.handleSuccess.bind(this));
Copy link
Contributor

Choose a reason for hiding this comment

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

Interesting, this required a change to done? In reading the guide I would've thought then would still be preferred as that is the new way forward with the Deferred object changes. It appears we're still using the old style, though, according to this part, which would make sense given this change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, I was confused about this too. But there was an issue with the wrong context not being passed and this solution fixed it. Since it's a test and not a feature, seemed ok to just leave it.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good to me! Should we work in the fec-style version bump in this PR to just ensure full testing of the updates?

Copy link
Contributor Author

@noahmanger noahmanger May 10, 2017

Choose a reason for hiding this comment

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

Sounds good.

@ccostino ccostino merged commit e9774df into develop May 10, 2017
@ccostino ccostino deleted the feature/jquery-upgrade branch May 10, 2017 17:40
@noahmanger noahmanger mentioned this pull request May 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants