Struct postman_collection::v1_0_0::Folder
source · pub struct Folder {
pub auth: Option<Auth>,
pub collection: Option<String>,
pub collection_id: Option<String>,
pub description: String,
pub events: Option<Vec<Event>>,
pub folders_order: Option<Vec<String>>,
pub id: String,
pub name: String,
pub order: Vec<String>,
pub variables: Option<Vec<Variable>>,
}
Expand description
One of the primary goals of Postman is to organize the development of APIs. To this end, it is necessary to be able to group requests together. This can be achived using ‘Folders’. A folder just is an ordered set of requests.
Fields§
§auth: Option<Auth>
§collection: Option<String>
Postman folders are always a part of a collection. That collection’s unique ID (which is a UUID) is stored in this field.
collection_id: Option<String>
Postman folders are always a part of a collection. That collection’s unique ID (which is a UUID) is stored in this field.
description: String
Essays about the folder go into this field!
events: Option<Vec<Event>>
§folders_order: Option<Vec<String>>
Postman preserves the order of your folders within each folder. This field holds a sequence of UUIDs, where each ID corresponds to a particular collection folder.
id: String
In order to be able to uniquely identify different folders within a collection, Postman assigns each folder a unique ID (a UUID). This field contains that value.
name: String
A folder’s friendly name is defined by this field. You would want to set this field to a value that would allow you to easily identify this folder.
order: Vec<String>
Postman preserves the order of your requests within each folder. This field holds a sequence of UUIDs, where each ID corresponds to a particular Postman request.
variables: Option<Vec<Variable>>