[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:
causality
is causing MGNLRESTCL-68 RestClient has ability to add query p... Closed
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 MGNLRESTCL-42 answered the last AC (passing specific params), it looks a bit too verbose to do so (and a bit too powerful too): being able to override entire path, query-params and request body from the original definition.

We should try to leverage templateValues for that:

  • support placeholders such as {id} not only in path, but also in queryParams and body
  • pass them as a map to the invoke and/or restfn calls
  • take care about escaping/quoting arguments


 Comments   
Comment by Christopher Zimmermann [ 09/Sep/19 ]

Is the original AC still implemented, or does this ticket remove it? 

  • I can use a REST Client, and if I do I can provide custom path fragments and query parameters to use in the REST call.

 

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.
Adding new query or header parameters that have not previously been defined in the yaml definition is not supported with this ticket

Generated at Mon Feb 12 10:42:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.