You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
name: Markdown code block with variables syntax support to keyword for response
about: It would be useful to support variable syntax in the response block, within markdown code blocks in the REST Client. This would allow users to define and reference variables within code blocks without breaking syntax highlighting or requiring workarounds. Currently, variables are supported within request files but are not properly recognized inside markdown code blocks. Supporting this feature would:
Improve readability and maintainability of requests documented in markdown.
Enhance the user experience when writing API documentation with embedded requests.
Reduce the need for escaping or alternate syntax workarounds.
Expected Behavior
The {{token}} variable must be able to be extracted from the authentication response and used in subsequent requests, using only the "response:" keyword in the http block of the request, ending the request and starting the response, thus being able to read the returned values. This feature would benefit users who document APIs extensively in markdown while leveraging REST Client capabilities.
name: Markdown code block with variables syntax support to keyword for response
about: It would be useful to support variable syntax in the response block, within markdown code blocks in the REST Client. This would allow users to define and reference variables within code blocks without breaking syntax highlighting or requiring workarounds. Currently, variables are supported within request files but are not properly recognized inside markdown code blocks. Supporting this feature would:
Expected Behavior
The {{token}} variable must be able to be extracted from the authentication response and used in subsequent requests, using only the "response:" keyword in the http block of the request, ending the request and starting the response, thus being able to read the returned values. This feature would benefit users who document APIs extensively in markdown while leveraging REST Client capabilities.
Example of how it should work:
The text was updated successfully, but these errors were encountered: