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
Under the "Try It" request samples when there are URL parameters required in the endpoint, the current behavior is to substitute the URL parameter's name into the URL until a value is entered. Once the value is entered, the value is used instead.
When no value is entered, curly brackets should be included around the parameter's name to make it clear that the value should be replaced.
Context
Clarify the "Try It" code samples when no parameters have been entered.
Change from showing the endpoint url as https://api.example.com/users/userId to https://api.example.com/users/{userId}
Current Behavior
Currently if no details have been entered in the URL parameter, it shows the URL parameter's name in the URL.
Expected Behavior
The URL parameter would be wrapped in {} until the user inputs some value.
Possible Solution(s)
If this is a change that others feel is worthwhile, I'm happy to look into implementation details.
The text was updated successfully, but these errors were encountered:
Under the "Try It" request samples when there are URL parameters required in the endpoint, the current behavior is to substitute the URL parameter's name into the URL until a value is entered. Once the value is entered, the value is used instead.
When no value is entered, curly brackets should be included around the parameter's name to make it clear that the value should be replaced.
Context
Clarify the "Try It" code samples when no parameters have been entered.

Change from showing the endpoint url as
https://api.example.com/users/userId
tohttps://api.example.com/users/{userId}
Current Behavior
Currently if no details have been entered in the URL parameter, it shows the URL parameter's name in the URL.
Expected Behavior
The URL parameter would be wrapped in
{}
until the user inputs some value.Possible Solution(s)
If this is a change that others feel is worthwhile, I'm happy to look into implementation details.
The text was updated successfully, but these errors were encountered: