support to render object

[NingGelin]

Problem to solve

my hurl file

POST {{host}}/partyManagement/v5/individual
{
  "@type": "Individual",
  "@baseType": "Party",
  "givenName": "Jane-us0001-ac1-{{postfix}}",
  "familyName": "Lamborgizzia-us0001-ac1-{{postfix}}"
}
HTTP 201
[Captures]
response: jsonpath "$"

POST {{host}}/customerManagement/v5/customer
{{response}}
HTTP 201

Proposal

I want to extract a object from response last step then render it in next step. It seem like not supported currently. If I missed something, please correct me. Thank you very much.

Additional context and resources

[fabricereix]

Hi @NingGelin
yes this is not supported yet.
you can have a look at #2152

[jcamiel]

In this particular use case (you want to render the full body), you can also capture the full body (which has a text type)

POST {{host}}/partyManagement/v5/individual
{
  "@type": "Individual",
  "@baseType": "Party",
  "givenName": "Jane-us0001-ac1-{{postfix}}",
  "familyName": "Lamborgizzia-us0001-ac1-{{postfix}}"
}
HTTP 201
[Captures]
response: body

POST {{host}}/customerManagement/v5/customer
{{response}}
HTTP 201

It "should" work (I've not tested it)

[NingGelin]

In this particular use case (you want to render the full body), you can also capture the full body (which has a text type)

POST {{host}}/partyManagement/v5/individual
{
  "@type": "Individual",
  "@baseType": "Party",
  "givenName": "Jane-us0001-ac1-{{postfix}}",
  "familyName": "Lamborgizzia-us0001-ac1-{{postfix}}"
}
HTTP 201
[Captures]
response: body

POST {{host}}/customerManagement/v5/customer
{{response}}
HTTP 201

It "should" work (I've not tested it)

not work. thank you anyway

[jcamiel]

Ah sorry @NingGelin , you can use multiline string body, that should do the trick. You can put a hint with the json tag to send the right application/json Content-Type header:

POST {{host}}/partyManagement/v5/individual
{
  "@type": "Individual",
  "@baseType": "Party",
  "givenName": "Jane-us0001-ac1-{{postfix}}",
  "familyName": "Lamborgizzia-us0001-ac1-{{postfix}}"
}
HTTP 201
[Captures]
response: body

POST {{host}}/customerManagement/v5/customer
```json
{{response}}
```
HTTP 201

[juan-m-medina]

Ah sorry @NingGelin , you can use multiline string body, that should do the trick. You can put a hint with the json tag to send the right application/json Content-Type header:

POST {{host}}/partyManagement/v5/individual
{
  "@type": "Individual",
  "@baseType": "Party",
  "givenName": "Jane-us0001-ac1-{{postfix}}",
  "familyName": "Lamborgizzia-us0001-ac1-{{postfix}}"
}
HTTP 201
[Captures]
response: body

POST {{host}}/customerManagement/v5/customer
```json
{{response}}

HTTP 201

While this works for the full body, it won't work for a jsonpath extract - with or without the multi-line hint.

GET https://jsonplaceholder.typicode.com/posts

HTTP 200
[Captures]
first_post: jsonpath "$[0]"

PUT https://jsonplaceholder.typicode.com/posts/1
{{first_post}}
HTTP 200

[jcamiel]

Hi @juan-m-medina

Rendering a variable captured by JSONPath query (like {{first_post}}) is not yet supported. As a workaround until a proper solution is implemented, you can split your captures :

GET https://jsonplaceholder.typicode.com/posts
HTTP 200
[Captures]
first_post_name: jsonpath "$[0].name"
first_post_description: jsonpath "$[0].description"
first_post_publication_date: jsonpath "$[0].publication_date"


PUT https://jsonplaceholder.typicode.com/posts/1
{ 
  "name:" {{first_post_name}},
  "description": {{first_post_description}},
  "publication_date": {{first_post_publication_date}}
}
HTTP 200