Challenge 2: Chain a Named Request — Possible Solution
====================================================================

# @name createOrder
POST {{baseUrl}}/orders
Content-Type: application/json

{
  "productId": "P200",
  "quantity": 1
}

###

GET {{baseUrl}}/orders/{{createOrder.response.body.$.id}}

WHY THIS WORKS AS AN ANSWER
------------------------------
# @name createOrder labels the first request, exactly like the
chapter's # @name login example — this is what makes its response
available for the second request to reference at all.

The second request's URL embeds
{{createOrder.response.body.$.id}} directly in the URL PATH, not just
in a header — this mirrors the fact that an order's id needs to become
part of the GET request's actual URL (/orders/O5521), not sent as a
separate header the way an auth token was in the chapter's own
example. The {{label.response.body.$.field}} syntax works the same way
regardless of where in the request it's used — URL, header, or body —
since it's simply substituted as plain text wherever it appears.

The ### separator between the two requests is required, the same as
any other multi-request .http file — without it, the extension would
treat both requests as one malformed block.