[MGNLRESTCL-157] Request body content-type should be explicitly defined in RestCall definition. Created: 21/Apr/20 Updated: 28/Jun/22 |
|
| Status: | Open |
| Project: | REST Client |
| Component/s: | API |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Quach Hao Thien | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Epic Link: | RestClient Maintenance |
| Description |
|
As a RestClient consumer, I want to define the content-type of request body explicitly in yaml definition to make it more descriptive instead using header's content-type. Acceptance criteria
Current baseUrl: http://localhost:${wiremockPort} restCalls: createNewArticle: method: POST entityClass: java.lang.String responseContentType: application/json path: /createNew body: {content} headers: Content-Type: multipart/form-data If request header content-type is missing, the "application/json" content-type is set by default on backend Expect baseUrl: http://localhost:${wiremockPort} restCalls: createNewArticle: method: POST entityClass: java.lang.String responseContentType: application/json path: /createNew body: content: {content} contentType: multipart/form-data headers: Content-Type: application/json << this will be overridden by body contentType
|