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

Reimplementation of most of the pull requests and open issues #141

Closed
wants to merge 15 commits into from
Closed

Reimplementation of most of the pull requests and open issues #141

wants to merge 15 commits into from

Conversation

dennissivia
Copy link

No description provided.

Dennis Sivia and others added 15 commits February 29, 2016 16:44
In order to make it easier to merge other pull requests,
we should update to rspec 3.
This PR updats the Gemfile.lock to use rspec 3.4, it also
updats the test syntax to match the new rspec testing style.

This Change has been ported from
[this contribution](https://github.com/brynary/rack-test/pull/134/commits)
Update to latest rspec version and syntax.
Thanks to davidcelis.
Implements: [PR 132](#132)
…tent-type-for-deletes

Do not set Content-Type for DELETE requests.
expose Rack::Test::Utils methods as module functions to avoid
a mixing requirement of utility functions.

Implements PR #131. Thanks to @tenderlove for implementing this
feature.
…tipart-work-without-include

Make `build_multipart` work without mixing in Rack::Test::Utils
Without the patch empty arrays will be removed implicitly.
Adding this special case to ``build_nested_query`` fixes this
issue.

Implements PR #125, thanks to @croeck and @Timsly
…r-empty-arrays-in-params

Adds support for empty arrays in params.
Adds intialization of digest_username and digest_password.

Implements PR #116 and PR #124 .
…est-username

Initialize digest_username before using it.
@dennissivia
Copy link
Author

@brynary is there any chance that this will be merged or that somebody will get contribution permission?

@brynary
Copy link
Collaborator

brynary commented Jun 9, 2016

Hey! Yes, sorry for the long delay. Can anyone validate these changes are good? The test suite is pretty solid but would good to have some additional validation for a large PR.

@dennissivia
Copy link
Author

Is there any update here so far? I guess most of the changes have already been reviewed before, since this PR is just bundling a bunch of other open PRs to make them compatible.

@perlun
Copy link
Contributor

perlun commented Apr 26, 2017

@scepticulous I think this got included now when I rebased your changes on top of master (once @brynary had moved the repo to the rack-test organization), so will close this. If you still feel something is missing, just create a new PR and we'll deal with it then.

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.

3 participants