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
Differentiate postman folder from request when at collection root (#3912)
* Modified scanItem to keep track of parent folder and eliminate folder info being identical to request info
* Use UID for parent ID and request ID for consistency
* Updated description of UID
* Added commentary for parent folder ID business
// The assignment of the folder ID to be the current item UID is due to wanting to assume that your current item is a folder unless you have request data inside of your item.
359
+
// If your current item is a folder, you will want the folder ID to match the UID of the current item.
360
+
// If your current item is a request, you will want the folder ID to match the UID of the parent folder.
361
+
// If the request is at the root of a collection and has no parent folder, the folder ID will be empty.
Copy file name to clipboardExpand all lines: pkg/sources/postman/postman_client.go
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ type Item struct {
109
109
RequestRequest`json:"request,omitempty"`
110
110
Response []Response`json:"response,omitempty"`
111
111
Descriptionstring`json:"description,omitempty"`
112
-
UIDstring`json:"uid,omitempty"`//Need to use this to get the collection via API
112
+
UIDstring`json:"uid,omitempty"`//Need to use this to get the collection via API. The UID is a concatenation of the ID and the user ID of whoever created the item.
0 commit comments