item-group can contains a "_postman_isSubFolder" attribute

[jmini]

When an Item into a sub-sub folder (a.k.a item-group):

The corresponding exported collection is:

{
	"info": {
		"_postman_id": "4e034bd9-dc3b-427b-ba77-83a8ecc9cdc8",
		"name": "example",
		"description": "This is an example",
		"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
	},
	"item": [
		{
			"name": "foo",
			"item": [
				{
					"name": "bar",
					"item": [
						{
							"name": "Echo",
							"protocolProfileBehavior": {
								"strictSSL": true
							},
							"request": {
								"method": "GET",
								"header": [],
								"url": {
									"raw": "https://postman-echo.com/get",
									"protocol": "https",
									"host": [
										"postman-echo",
										"com"
									],
									"path": [
										"get"
									]
								}
							},
							"response": []
						}
					],
					"protocolProfileBehavior": {},
					"_postman_isSubFolder": true
				}
			],
			"event": [],
			"protocolProfileBehavior": {}
		}
	],
	"event": [],
	"protocolProfileBehavior": {}
}

As you can see on line 39, there is a _postman_isSubFolder attribute (boolean value).

But the schema doesn't describes this _postman_isSubFolder attribute, inside the properties map:

schemas/schemas/draft-04/v2.1.0/collection/item-group.json

Line 7 in e6429ea

"properties": {

[codenirvana]

Looks like this is a bug in the collection export/transformation module.

[jmini]

@codenirvana: thank you for the feedback.

Is there already an issue for the broken export function in the Postman app?

Do I get this right that you don't want have this field documented in the schema, because it is a bug in the first place?
On the other side, there are already collections exported with this attribute. Having this attribute absent from the schema makes them all invalid…

[jviotti]

@jmini

On the other side, there are already collections exported with this attribute. Having this attribute absent from the schema makes them all invalid…

Keep in mind that the schemas don't seem to define additionalProperties: false, and extra properties not defined in the schema are permitted by default by JSON Schema, so having them there is actually not invalid.