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

Add optional contentType to formDsl #910

Merged
merged 2 commits into from
Feb 13, 2019

Conversation

wollnyst
Copy link
Contributor

Fixes #766

IMO it's enough to add ContentType, that covers like 99% of upload scenarios now. For all other scenarios we can use append(key, headers,, bodyBuilder)

@e5l e5l self-requested a review February 1, 2019 09:56
@e5l
Copy link
Member

e5l commented Feb 1, 2019

Hi @wollnyst, thanks for the PR.
Could you add the test with contentType?

@wollnyst
Copy link
Contributor Author

wollnyst commented Feb 4, 2019

Done.

@e5l e5l changed the base branch from master to e5l/develop February 13, 2019 10:16
@e5l
Copy link
Member

e5l commented Feb 13, 2019

Merged into develop to verify binary compatibility.

@e5l e5l merged commit e783c53 into ktorio:e5l/develop Feb 13, 2019
e5l pushed a commit that referenced this pull request Feb 21, 2019
* Add optional contentType to formDsl

* Tests for contentType in formDsl
e5l pushed a commit that referenced this pull request Feb 25, 2019
* Add optional contentType to formDsl

* Tests for contentType in formDsl
e5l pushed a commit that referenced this pull request Feb 25, 2019
* Add optional contentType to formDsl

* Tests for contentType in formDsl
e5l pushed a commit that referenced this pull request Feb 26, 2019
* Add optional contentType to formDsl

* Tests for contentType in formDsl
schleinzer pushed a commit to schleinzer/ktor that referenced this pull request Feb 26, 2019
* Add optional contentType to formDsl

* Tests for contentType in formDsl
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.

2 participants