[MGNLRESTCL-105] Remove unnecessary api from rest client and restfn that was recently introduced Created: 26/Nov/19 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | REST Client |
| Component/s: | None |
| Affects Version/s: | 2.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
New method with body parameter was recently introduced into the api of rest client. Response invoke(String restCallName, Object body, Map<String, Object> additionalDefaultValues); In fact, such introduction is not needed because whole body object can be safely set using additionalDefaultValues. Example:
baseUrl: https://some.api
restCalls:
myRestCallWithBody:
path: /some/path
method: post
body: {body}
and template: [#assign mySuperLongBody = "{.......}"] [#assign result = restfn.call("client", "myRestCallWithBody", {body: mySuperLongBody)] Method should be also removed from restfn. |