Skip to content
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

Fix for .pipe method after the update to 1.7 #4

Merged
merged 1 commit into from Jan 5, 2012

Conversation

taxilian
Copy link
Contributor

@taxilian taxilian commented Jan 5, 2012

I guess I didn't test as well as I thought; .pipe was completely broken.

it is fixed in this pull request; hoping you can get it up really fast 'cause I need to get it to my team ASAP but need it in npm first ;-)

@@ -274,7 +277,7 @@
done: [ fnDone, "resolve" ],
fail: [ fnFail, "reject" ],
progress: [ fnProgress, "notify" ]
}, function( handler, data ) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hummmm... Do we really need to complicate things by defining _each when _each is only used once here. This is a trivial process to iterate over the keys and in a for loop. I suppose this refactoring this part to be non-functional will further deviate from jQueries 1.7 source, but the positive side would be _each and line 4 can be completely removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's your call; I would suggest accepting this for now, though, and then refactoring if you decide you want to. I'm not concerned about the code size on the server, but I am concerned about the functionality =]

The only reason for doing it this way is, as you say, to remain as close as possible to jquery source.

ryanstevens added a commit that referenced this pull request Jan 5, 2012
Fix for .pipe method after the update to 1.7
@ryanstevens ryanstevens merged commit 45bc4df into watcherdm:master Jan 5, 2012
@watcherdm
Copy link
Owner

just a note, this has now been pushed to npm at 0.1.1

@taxilian
Copy link
Contributor Author

taxilian commented Jan 5, 2012

thank you much!

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

Successfully merging this pull request may close these issues.

None yet

3 participants