[MGNLRESTCL-67] Improve isolation of params between definition and invocations Created: 27/Aug/19 Updated: 10/Sep/19 Resolved: 09/Sep/19 |
|
| Status: | Closed |
| Project: | REST Client |
| Component/s: | API |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Andrei Ichimescu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Declarative REST clients | ||||||||
| Sprint: | Declarative REST 5 | ||||||||
| Story Points: | 8 | ||||||||
| Description |
|
While We should try to leverage templateValues for that:
|
| Comments |
| Comment by Christopher Zimmermann [ 09/Sep/19 ] |
|
Is the original AC still implemented, or does this ticket remove it?
|
| Comment by Andrei Ichimescu [ 09/Sep/19 ] |
|
With this ticket, you can provide custom path fragments and query parameters `e.g: queryParam1:{queryValue1}` to use in the REST call. On top of that, custom headers `e.g: Accept:{acceptHeader}` and custom body fragments are also supported. |