Request Samples Shell - cURL URL with incorrect suffix in the first example after updating to V2.7.2

Bug Report
1

After updating to version 2.7.2, when adding new request examples to our API documentation, the first Shell / cURL code example always presents an incorrect URL. The documented endpoint receives an unintended suffix at the end:

?members&reference&Type&_postman_listIndexKey=key&_postman_listAllowsMultipleValues

We tried removing and re-adding the examples, but the issue persists in the first example.

Could you please check?

chrome_Ns5fJIFeRm.png
chrome_Ns5fJIFeRm.png1920×911 123 KB

2

Hello. Currently, I haven’t reproduced the issue you mentioned in the published document. Could you please provide more details such as your sample code settings for the endpoint and the link to the document to help us locate the problem?

image.jpg
image.jpg2930×888 163 KB