[MGNLRESTCL-104] Request body is always assumed to be a JSON Created: 26/Nov/19 Updated: 13/Dec/19 Resolved: 27/Nov/19 |
|
| Status: | Closed |
| Project: | REST Client |
| Component/s: | None |
| Affects Version/s: | 2.0 |
| Fix Version/s: | 2.0 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Jaroslav Simak |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 3h | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Epic Link: | Declarative REST clients |
| Sprint: | Declarative REST 11 |
| Story Points: | 2 |
| Description |
|
Due to the fact that we always assume that body of the request is JSON, we can't use any other body types, such as application/graphql or application/xml. While working on the presentation, we decided to include graphql example from Shopify. Due to the limitation described above, graphql cannot be used. |