@forge/manifest 6.2.0-next.3 → 6.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +20 -0
  2. package/out/schema/manifest-schema.json +0 -76
  3. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,25 @@
1
1
  # @forge/manifest
2
2
 
3
+ ## 6.2.0
4
+
5
+ ### Minor Changes
6
+
7
+ - 9307e05: Added endpoint validation for bitbucket:mergeCheck module
8
+
9
+ ### Patch Changes
10
+
11
+ - f9492fb: Update manifest definitions
12
+ - 2f32562: Update manifest definitions
13
+ - afbb875: Update manifest definitions
14
+ - Updated dependencies [d76d95c]
15
+ - @forge/util@1.4.2
16
+
17
+ ## 6.2.0-next.4
18
+
19
+ ### Patch Changes
20
+
21
+ - afbb875: Update manifest definitions
22
+
3
23
  ## 6.2.0-next.3
4
24
 
5
25
  ### Patch Changes
package/out/schema/manifest-schema.json CHANGED
@@ -10303,7 +10303,6 @@
10303
10303
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
10304
10304
  },
10305
10305
  "url": {
10306
- "format": "uri",
10307
10306
  "type": "string",
10308
10307
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
10309
10308
  },
@@ -10381,7 +10380,6 @@
10381
10380
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
10382
10381
  },
10383
10382
  "url": {
10384
- "format": "uri",
10385
10383
  "type": "string",
10386
10384
  "fieldDescription": "\n\nThe URL of the add-on resource that provides the web panel content. This URL must be relative to the add-on's \n baseUrl and can use <a href=\"../../context-parameters/\">context parameters</a>.\n\n"
10387
10385
  },
@@ -10514,7 +10512,6 @@
10514
10512
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
10515
10513
  },
10516
10514
  "url": {
10517
- "format": "uri",
10518
10515
  "type": "string",
10519
10516
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
10520
10517
  },
@@ -10644,7 +10641,6 @@
10644
10641
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
10645
10642
  },
10646
10643
  "url": {
10647
- "format": "uri",
10648
10644
  "type": "string",
10649
10645
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
10650
10646
  },
@@ -11036,7 +11032,6 @@
11036
11032
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
11037
11033
  },
11038
11034
  "url": {
11039
- "format": "uri",
11040
11035
  "type": "string",
11041
11036
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
11042
11037
  },
@@ -11307,7 +11302,6 @@
11307
11302
  "defaultValue": "100"
11308
11303
  },
11309
11304
  "iconUrl": {
11310
- "format": "uri",
11311
11305
  "type": "string",
11312
11306
  "fieldDescription": "\n\nSpecifies an icon URL that will displayed alongside the link to the project page in the project sidebar.\n\n The icon resource provided in this field should be larger or equals to 16x16 pixels.<br>\n\n"
11313
11307
  },
@@ -11327,7 +11321,6 @@
11327
11321
  "fieldDescription": "\n\n<a href=\"../../conditions/\">Conditions</a> can be added to display only when all the given conditions are true.\n\n"
11328
11322
  },
11329
11323
  "url": {
11330
- "format": "uri",
11331
11324
  "type": "string",
11332
11325
  "fieldDescription": "\n\nSpecifies the URL targeted by the page. The URL is relative to the add-on's base URL.\n\n"
11333
11326
  },
@@ -11476,7 +11469,6 @@
11476
11469
  "fieldDescription": "\n\nThe type field must be set to 'web_panel'\n\n"
11477
11470
  },
11478
11471
  "url": {
11479
- "format": "uri",
11480
11472
  "type": "string",
11481
11473
  "fieldDescription": "\n\nThe URL of the app resource that provides the web panel content. This URL must be relative to the app's baseUrl.\n\n"
11482
11474
  }
@@ -11631,7 +11623,6 @@
11631
11623
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
11632
11624
  },
11633
11625
  "url": {
11634
- "format": "uri",
11635
11626
  "type": "string",
11636
11627
  "fieldDescription": "\n\nSpecifies the URL targeted by the tab panel. The URL is relative to the add-on's base URL.\n\n"
11637
11628
  },
@@ -11789,7 +11780,6 @@
11789
11780
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
11790
11781
  },
11791
11782
  "url": {
11792
- "format": "uri",
11793
11783
  "type": "string",
11794
11784
  "fieldDescription": "\n\nSpecifies the URL targeted by the tab panel. The URL is relative to the add-on's base URL.\n\n"
11795
11785
  },
@@ -11917,7 +11907,6 @@
11917
11907
  "fieldDescription": "\n\nURL to the provider's homepage\n\n"
11918
11908
  },
11919
11909
  "documentationUrl": {
11920
- "format": "uri",
11921
11910
  "type": "string",
11922
11911
  "fieldDescription": "\n\nOptional URL to documentation about the provider's Jira integration\n\n"
11923
11912
  },
@@ -11948,7 +11937,6 @@
11948
11937
  "fieldDescription": "\n\n<p>The actionLabel of an Action is shown visibly to the User alongside the Remote Link.</p>\n\n"
11949
11938
  },
11950
11939
  "templateUrl": {
11951
- "format": "uri",
11952
11940
  "type": "string",
11953
11941
  "fieldDescription": "\n\n<p>The templateUrl of an Action is a template where strings can be substituted into the URL for a specific Remote Link. Strings used in the templateUrl must be passed in via an attribute map when associating an action with a remote link.</p>\n\n"
11954
11942
  }
@@ -12011,7 +11999,6 @@
12011
11999
  "fetchWorkspaces": {
12012
12000
  "properties": {
12013
12001
  "templateUrl": {
12014
- "format": "uri",
12015
12002
  "type": "string",
12016
12003
  "fieldDescription": "\n\n"
12017
12004
  }
@@ -12026,7 +12013,6 @@
12026
12013
  "fetchContainers": {
12027
12014
  "properties": {
12028
12015
  "templateUrl": {
12029
- "format": "uri",
12030
12016
  "type": "string",
12031
12017
  "fieldDescription": "\n\n"
12032
12018
  }
@@ -12041,7 +12027,6 @@
12041
12027
  "searchContainers": {
12042
12028
  "properties": {
12043
12029
  "templateUrl": {
12044
- "format": "uri",
12045
12030
  "type": "string",
12046
12031
  "fieldDescription": "\n\n"
12047
12032
  }
@@ -12056,7 +12041,6 @@
12056
12041
  "onEntityAssociated": {
12057
12042
  "properties": {
12058
12043
  "templateUrl": {
12059
- "format": "uri",
12060
12044
  "type": "string",
12061
12045
  "fieldDescription": "\n\n"
12062
12046
  }
@@ -12071,7 +12055,6 @@
12071
12055
  "onEntityDisassociated": {
12072
12056
  "properties": {
12073
12057
  "templateUrl": {
12074
- "format": "uri",
12075
12058
  "type": "string",
12076
12059
  "fieldDescription": "\n\n"
12077
12060
  }
@@ -12161,7 +12144,6 @@
12161
12144
  ]
12162
12145
  },
12163
12146
  "url": {
12164
- "format": "uri",
12165
12147
  "type": "string",
12166
12148
  "fieldDescription": "\n\nThe URL of the app resource that serves the iframe containing the background script.\n As with other app iframes, the iframe must load all.js.\n This URL does not support [context parameters](/cloud/jira/platform/context-parameters/).\n This URL must be relative to the app's baseUrl.\n\n"
12167
12149
  },
@@ -12270,12 +12252,10 @@
12270
12252
  "defaultValue": "other"
12271
12253
  },
12272
12254
  "url": {
12273
- "format": "uri",
12274
12255
  "type": "string",
12275
12256
  "fieldDescription": "\n\nSpecifies the URL targeted by the report. The URL is relative to the add-on's base URL.\n\n"
12276
12257
  },
12277
12258
  "thumbnailUrl": {
12278
- "format": "uri",
12279
12259
  "type": "string",
12280
12260
  "fieldDescription": "\n\nSpecifies the URL of the report thumbnail. The URL is relative to the add-on's base URL.\n\n"
12281
12261
  },
@@ -12369,7 +12349,6 @@
12369
12349
  "fieldDescription": "\n\nThe type field must be set to 'web_panel'\n\n"
12370
12350
  },
12371
12351
  "url": {
12372
- "format": "uri",
12373
12352
  "type": "string",
12374
12353
  "fieldDescription": "\n\nThe URL of the app resource that provides the web panel content. This URL must be relative to the app's baseUrl.\n\n"
12375
12354
  }
@@ -12437,7 +12416,6 @@
12437
12416
  "fieldDescription": "\n\n<a href=\"../../conditions/\">Conditions</a> can be added to display only when all the given conditions are true.\n\n"
12438
12417
  },
12439
12418
  "url": {
12440
- "format": "uri",
12441
12419
  "type": "string",
12442
12420
  "fieldDescription": "\n\nThe URL of the service which will render the dashboard item. Following context parameters are supported in\n url.\n\n * `dashboard.id` unique id of the dashboard on which the item is rendered. This parameter is passed only on default view\n * `dashboardItem.id` unique id of the dashboard item which is rendered. This parameter is passed only on default view\n * `dashboardItem.key` key of the dashboard item. This parameter is passed in both: default and directory view\n * `dashboardItem.viewType` type of the view in which dashboard item is displayed. Default (for dashboard) and directory. This list may be extended\n\n"
12443
12421
  },
@@ -12452,7 +12430,6 @@
12452
12430
  "defaultValue": "false"
12453
12431
  },
12454
12432
  "thumbnailUrl": {
12455
- "format": "uri",
12456
12433
  "type": "string",
12457
12434
  "fieldDescription": "\n\nURI of the dashboard item thumbnail which is displayed in the directory.\n\n"
12458
12435
  },
@@ -12564,7 +12541,6 @@
12564
12541
  "fieldDescription": "\n\nThe type field must be set to 'web_panel'\n\n"
12565
12542
  },
12566
12543
  "url": {
12567
- "format": "uri",
12568
12544
  "type": "string",
12569
12545
  "fieldDescription": "\n\nThe URL of the add-on resource that provides the web panel content.\n This URL must be relative to the app's baseUrl.\n\n"
12570
12546
  }
@@ -12793,7 +12769,6 @@
12793
12769
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
12794
12770
  },
12795
12771
  "url": {
12796
- "format": "uri",
12797
12772
  "type": "string",
12798
12773
  "fieldDescription": "\n\nSpecifies the URL targeted by the tab panel. The URL is relative to the add-on's base URL.\n\n"
12799
12774
  },
@@ -13085,12 +13060,10 @@
13085
13060
  "items": {
13086
13061
  "properties": {
13087
13062
  "installed": {
13088
- "format": "uri",
13089
13063
  "type": "string",
13090
13064
  "fieldDescription": "\n\nWhen a Connect add-on is installed, a synchronous request is fired to this URL to initiate the installation\n handshake. In order to successfully complete installation, the add-on must respond with either a\n <code>200 OK</code> or <code>204 No Content</code> status.\n\n<div class=\"aui-message warning\">\n <p class=\"title\">\n <span class=\"aui-icon icon-warning\">Warning</span>\n <strong>Important</strong>\n </p>\n Upon successful registration, the add-on must return either a <code>200 OK</code> or <code>204 No Content</code>\n response code, otherwise the operation will fail and the installation will be marked as incomplete.\n</div>\n\n"
13091
13065
  },
13092
13066
  "disabled": {
13093
- "format": "uri",
13094
13067
  "type": "string",
13095
13068
  "fieldDescription": "\n\nFires when an add on has been successfully disabled. This is an asynchronous notification event.\n\n"
13096
13069
  },
@@ -13099,12 +13072,10 @@
13099
13072
  "fieldDescription": "\n\nUsed DaRe app migration service to trigger migrations events\n\n"
13100
13073
  },
13101
13074
  "uninstalled": {
13102
- "format": "uri",
13103
13075
  "type": "string",
13104
13076
  "fieldDescription": "\n\nFires when an add on has been successfully un-installed. This is an asynchronous notification event.\n\n"
13105
13077
  },
13106
13078
  "enabled": {
13107
- "format": "uri",
13108
13079
  "type": "string",
13109
13080
  "fieldDescription": "\n\nFires when an add on has been successfully enabled. This is an asynchronous notification event.\n\n"
13110
13081
  },
@@ -13128,7 +13099,6 @@
13128
13099
  "items": {
13129
13100
  "properties": {
13130
13101
  "url": {
13131
- "format": "uri",
13132
13102
  "type": "string"
13133
13103
  },
13134
13104
  "weight": {
@@ -13195,7 +13165,6 @@
13195
13165
  "items": {
13196
13166
  "properties": {
13197
13167
  "url": {
13198
- "format": "uri",
13199
13168
  "type": "string"
13200
13169
  },
13201
13170
  "weight": {
@@ -13262,7 +13231,6 @@
13262
13231
  "items": {
13263
13232
  "properties": {
13264
13233
  "url": {
13265
- "format": "uri",
13266
13234
  "type": "string"
13267
13235
  },
13268
13236
  "weight": {
@@ -13347,7 +13315,6 @@
13347
13315
  "type": "array"
13348
13316
  },
13349
13317
  "url": {
13350
- "format": "uri",
13351
13318
  "type": "string"
13352
13319
  },
13353
13320
  "key": {
@@ -13392,7 +13359,6 @@
13392
13359
  "type": "array"
13393
13360
  },
13394
13361
  "url": {
13395
- "format": "uri",
13396
13362
  "type": "string"
13397
13363
  },
13398
13364
  "key": {
@@ -13437,7 +13403,6 @@
13437
13403
  "type": "array"
13438
13404
  },
13439
13405
  "url": {
13440
- "format": "uri",
13441
13406
  "type": "string"
13442
13407
  },
13443
13408
  "key": {
@@ -13482,7 +13447,6 @@
13482
13447
  "type": "array"
13483
13448
  },
13484
13449
  "url": {
13485
- "format": "uri",
13486
13450
  "type": "string"
13487
13451
  },
13488
13452
  "key": {
@@ -13530,7 +13494,6 @@
13530
13494
  "type": "array"
13531
13495
  },
13532
13496
  "url": {
13533
- "format": "uri",
13534
13497
  "type": "string"
13535
13498
  },
13536
13499
  "key": {
@@ -13581,7 +13544,6 @@
13581
13544
  "type": "array"
13582
13545
  },
13583
13546
  "url": {
13584
- "format": "uri",
13585
13547
  "type": "string"
13586
13548
  },
13587
13549
  "key": {
@@ -13629,7 +13591,6 @@
13629
13591
  "type": "array"
13630
13592
  },
13631
13593
  "url": {
13632
- "format": "uri",
13633
13594
  "type": "string"
13634
13595
  },
13635
13596
  "key": {
@@ -13777,7 +13738,6 @@
13777
13738
  "type": "array"
13778
13739
  },
13779
13740
  "url": {
13780
- "format": "uri",
13781
13741
  "type": "string"
13782
13742
  },
13783
13743
  "key": {
@@ -13882,7 +13842,6 @@
13882
13842
  "type": "array"
13883
13843
  },
13884
13844
  "url": {
13885
- "format": "uri",
13886
13845
  "type": "string"
13887
13846
  },
13888
13847
  "key": {
@@ -13956,7 +13915,6 @@
13956
13915
  "icon": {
13957
13916
  "properties": {
13958
13917
  "url": {
13959
- "format": "uri",
13960
13918
  "type": "string"
13961
13919
  }
13962
13920
  },
@@ -14001,7 +13959,6 @@
14001
13959
  "type": "array"
14002
13960
  },
14003
13961
  "url": {
14004
- "format": "uri",
14005
13962
  "type": "string"
14006
13963
  },
14007
13964
  "key": {
@@ -14097,7 +14054,6 @@
14097
14054
  "type": "array"
14098
14055
  },
14099
14056
  "url": {
14100
- "format": "uri",
14101
14057
  "type": "string"
14102
14058
  },
14103
14059
  "key": {
@@ -14468,7 +14424,6 @@
14468
14424
  "fieldDescription": "\n\nThe list of arguments that the function accepts.\n\n"
14469
14425
  },
14470
14426
  "url": {
14471
- "format": "uri",
14472
14427
  "type": "string",
14473
14428
  "fieldDescription": "\n\nThe relative URL of the endpoint in the app that will be called by Jira to compute the function result.\n <p>\n The argument sent to the endpoint has the following format:\n <code><pre>\n {\n \"precomputationId\": \"<uuid>\"\n \"clause\": {\n \"field\": \"field name\",\n \"type\": [\n \"field type\"\n ],\n \"operator\": \"operator\",\n \"function\": \"function name\",\n \"arguments\": {\n \"value\"\n }\n }\n }\n\n </pre></code>\n <p>\n The endpoint is expected to return the result in the following format:\n <code><pre>\n {\n \"jql\": \"JQL fragment to use in place of the function clause\"\n }\n </pre></code>\n <p>\n or error message:\n <code><pre>\n {\n \"error\": \"Error message that will be displayed on the UI\"\n }\n </pre></code>\n"
14474
14429
  },
@@ -14610,7 +14565,6 @@
14610
14565
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
14611
14566
  },
14612
14567
  "url": {
14613
- "format": "uri",
14614
14568
  "type": "string",
14615
14569
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
14616
14570
  },
@@ -14688,7 +14642,6 @@
14688
14642
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
14689
14643
  },
14690
14644
  "url": {
14691
- "format": "uri",
14692
14645
  "type": "string",
14693
14646
  "fieldDescription": "\n\nThe URL of the add-on resource that provides the web panel content. This URL must be relative to the add-on's \n baseUrl and can use <a href=\"../../context-parameters/\">context parameters</a>.\n\n"
14694
14647
  },
@@ -14821,7 +14774,6 @@
14821
14774
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
14822
14775
  },
14823
14776
  "url": {
14824
- "format": "uri",
14825
14777
  "type": "string",
14826
14778
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
14827
14779
  },
@@ -14951,7 +14903,6 @@
14951
14903
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
14952
14904
  },
14953
14905
  "url": {
14954
- "format": "uri",
14955
14906
  "type": "string",
14956
14907
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
14957
14908
  },
@@ -15343,7 +15294,6 @@
15343
15294
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
15344
15295
  },
15345
15296
  "url": {
15346
- "format": "uri",
15347
15297
  "type": "string",
15348
15298
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This must be relative to the add-on's baseUrl.\n\n"
15349
15299
  },
@@ -15406,7 +15356,6 @@
15406
15356
  "blueprintContext": {
15407
15357
  "properties": {
15408
15358
  "url": {
15409
- "format": "uri",
15410
15359
  "type": "string",
15411
15360
  "fieldDescription": "\n\nA URL to which a POST request will be made during the rendering of the blueprint (see <a href=\"#POSTBODYEXAMPLE\">'Example of the request POST body' below</a> for an example\n of what will be POSTed to this resource). The response is then used for blueprint variable substitution, to enable\n blueprints to create pages that have dynamic content.\n <br>\n <h3>Expected response format</h3>\n The expected response from the context URL is a JSON array of objects with certain fields:\n\n\n\n\n\n [\n {\n \"identifier\": \"ContentPageTitle\",\n \"value\": \"Unique Page Title 1\",\n \"representation\": \"plain\"\n },\n {\n \"identifier\": \"custom-key1\",\n \"value\": \"custom value 1\",\n \"representation\": \"plain\"\n },\n {\n \"identifier\": \"custom-key2\",\n \"value\": \"<ac:structured-macro ac:name=\\\"cheese\\\" ac:schema-version=\\\"1\\\"/> \",\n \"representation\": \"storage\"\n }\n ]\n\n\n\n\n <h3 id=\"IDENTIFIERFIELD\">The <code>identifier</code> field</h3>\n The <code>identifier</code> field refers to the <code>name</code> attribute of the <code>var</code> element in a blueprint\n template. If the <code>identifier</code> is matched with a template variable, the <code>value</code> is used in the substitution.\n If a template contains a variable, but there is no matching <code>identifier</code> in the context, an error is generated.\n An identifier with no matching template variable is regarded as a no-op.\n\n The <code>identifier</code> field for each context object must be unique. It is an error to have more than one context object with\n the same identifier, and it is undefined which will get picked during substitution.\n\n\n Some <code>identifier</code> names are reserved for use with special meaning during substitution. They\n must have a <code>representation</code> field with the value <code>plain</code>. The list below describes the meaning\n of each existing reserved identifier.\n\n <ul>\n <li>\n <code>ContentPageTitle</code>: allows the blueprint template to set the page title. It must not contain any\n characters that cannot be used as a Confluence page title. If this reserved <code>identifier</code> is not\n found in the context, the page created from the blueprint will not have a title set and\n will require the user to set it before it can be saved. The blueprint module must also specify\n 'edit' as the value of the <code>createResult</code> field in this case. Note: the capital 'C'\n in the name is not a mistake or typo.\n </li>\n <li>\n <code>labelsString</code>: A space separated list of labels. The labels will be added to the page being created\n by this blueprint. See <a href=\"https://confluence.atlassian.com/display/doc/Add%2C+Remove+and+Search+for+Labels\">\n the Confluence docs about labels</a> for more information.\n </li>\n </ul>\n Using reserved identifiers as part of your template is possible, but these identifiers may change in the future, so\n best practice is to only use non-reserved identifiers in your template. See <a href=\"#BACKWARDSCOMPATIBILITY\">Backwards compatibility</a>\n for more information on <code>identifier</code>s.\n\n <h3>The <code>representation</code> field</h3>\n\n The <code>representation</code> field must be one of the following values. If unset, it will default to <code>plain</code>.\n <ul>\n <li><code>plain</code></li>\n <li><code>wiki</code></li>\n <li><code>storage</code></li>\n </ul>\n\n <h3>The <code>value</code> field</h3>\n\n The <code>value</code> field must be in the same format as the <code>representation</code> field.\n If the format is incorrect (such as mismatched tags in <code>storage</code> format), an error message will be displayed\n in the resulting page. Here's an explanation of what each format means:\n\n <ul>\n <li>\n <code>plain</code>: Plain text, which is HTML escaped during variable substitution. Use this for simple textual substitution.\n </li>\n <li>\n <code>wiki</code>: Valid <a href=\"https://confluence.atlassian.com/display/DOC/Confluence+Wiki+Markup\">\n Confluence Wiki Markup</a>. The wiki markup will be rendered into html during substitution into the page.\n The resulting page will not contain any wiki markup. Use this format when simple styling\n is required (such as emphasis, underlines or and tables etc).\n </li>\n <li>\n <code>storage</code>: Valid <a href=\"http://confluence.atlassian.com/display/DOC/Confluence+Storage+Format\">\n Confluence Storage Format</a>. This value is substituted into the page directly, before the page is rendered. Use this format\n to insert Confluence macros dynamically as part of your blueprint. See <a href=\"https://confluence.atlassian.com/display/DOC/Macros\">Macros</a>\n for a list of available Confluence macros, including storage format examples.\n </li>\n </ul>\n\n\n <h3 id=\"POSTBODYEXAMPLE\">Example of the request POST body</h3>\n The context url may need some information to produce a more individually suitable response. Confluence\n will send some information related to the blueprint in the body of the request during the creation process.\n Here's an example of what will be sent in the body of the POST request:\n\n\n\n\n\n {\n \"addonKey\": \"addon-key\",\n \"blueprintKey\": \"blueprint-key\",\n \"spaceKey\": \"SPACEKEY\",\n \"userKey\": \"edd16ba6-0d41-4313-8bb9-84dc82cf6e7c\",\n \"userLocale\": \"fr_FR\"\n }\n\n\n\n <ul>\n <li><code>addonKey</code>: the key of the add-on that the blueprint is part of.</li>\n <li><code>blueprintKey</code>: the key of the blueprint that triggered this context request.</li>\n <li><code>spaceKey</code>: the space to create the page in (this is selected by the user in the Create dialog).</li>\n <li><code>userKey</code>: the user key of the user creating the page from blueprint.</li>\n <li><code>userLocale</code>: the locale of the user creating the page from blueprint.</li>\n </ul>\n Note that userKey and userLocale will not be available in the POST request after GDPR deprecation period.\n\n"
15412
15361
  }
@@ -15421,7 +15370,6 @@
15421
15370
  "fieldDescription": "\n\nDefines the add-on server endpoint that provides the JSON objects used for substituting variables in the blueprint template.\n\n\n For more information on defining variables in blueprint templates, check out the examples in\n <a href=\"../blueprint-template-context/\">Blueprint Template Context</a>.\n\n"
15422
15371
  },
15423
15372
  "url": {
15424
- "format": "uri",
15425
15373
  "type": "string",
15426
15374
  "fieldDescription": "\n\nThe URL of the add-on resource that provides the blueprint template content. This URL has to be relative\n to the add-on base URL.\n\n"
15427
15375
  }
@@ -15569,7 +15517,6 @@
15569
15517
  "fieldDescription": "\n\nThis object represents a map of key/value pairs, where each property name and value corresponds to the parameter name and value respectively.\n\n <p><b>Example</b></p>\n\n\n\n\n\n {\n \"params\": {\n \"someOtherProperty\": \"someValue\",\n \"myCustomProperty\": \"myValue\"\n }\n }\n\n\n"
15570
15518
  },
15571
15519
  "url": {
15572
- "format": "uri",
15573
15520
  "type": "string",
15574
15521
  "fieldDescription": "\n\nThe url to retrieve the content from.\n This can be absolute or relative to the add-on's baseUrl\n\n"
15575
15522
  },
@@ -15747,7 +15694,6 @@
15747
15694
  "fieldDescription": "\n\n<a href=\"../../conditions/\">Conditions</a> can be added to display only when all the given conditions are true.\n\n"
15748
15695
  },
15749
15696
  "url": {
15750
- "format": "uri",
15751
15697
  "type": "string",
15752
15698
  "fieldDescription": "\n\nSpecifies the destination of the dialog content. The interpretation of this field depends on the value of the\n <pre>context</pre> field.\n\n Your add-on can receive [additional context](../../context-parameters/) from the app by\n using variable tokens in the URL attribute.\n\n"
15753
15699
  },
@@ -15862,7 +15808,6 @@
15862
15808
  "defaultValue": "false"
15863
15809
  },
15864
15810
  "url": {
15865
- "format": "uri",
15866
15811
  "type": "string",
15867
15812
  "fieldDescription": "\n\nThe URL to the macro configuration page in the add-on.\n\n"
15868
15813
  },
@@ -15948,7 +15893,6 @@
15948
15893
  "defaultValue": "block"
15949
15894
  },
15950
15895
  "url": {
15951
- "format": "uri",
15952
15896
  "type": "string",
15953
15897
  "fieldDescription": "\n\nThe link to the add-on resource that provides the macro content.\n This URL has to be relative to the add-on base URL.\n\n Additional context parameters can be passed as variables in the URL:\n <pre><code>\n {\n \"url\": \"/macro-renderer?body={macro.body}&amp;space_id={space.id}&amp;page_id={page.id}\"\n }\n </code></pre>\n\n Since macro bodies can be of arbitrary size and may contain sensitive data, care must be taken\n as to how its passed to your connect add-on. You have three options to gain access to the body:\n\n - If you can predict the size of your body and it is consistently less than 128 characters, you\n can include it in the GET request using the `{macro.body}` parameter.\n - If you know your macro contains a body that will often exceed the 128 character threshold\n (or is known to contain sensitive data), then you can include the `{macro.id}` parameter and\n use the Confluence REST api to call back to collect the body.\n - If you want, you can include, `{macro.body}`, `{macro.id}`, and `{macro.truncated}`. This way\n your plugin can call back to confluence only if `{macro.truncated}` is '`true`'. This will allow\n you to skip the callback if it's not needed. This would be useful for macros that don't\n contain sensitive data of an unpredictable size.\n\n\n__Note:__ If you include the `{macro.body}` in your URL you are potentially leaking sensitive data\n to any intermediate host on the internet. This may result in the body being cached or indexed\n by a third party. If you are concerned about the security of your macro, you should always use\n the `{macro.id}` and use the Confluence REST API to collect the body.\n\n Here's an example:\n\n Declare the variables that are later required to fetch the macro content in the URL:\n <pre><code>\n {\n \"url\": \"/render-macro?pageId={page.id}&amp;pageVersion={page.version}&amp;macroId={macro.id}\"\n }\n </code></pre>\n\n Then use the Confluence REST API to collect the body, for example directly from the iframe:\n <pre><code>\n AP.require(\"request\", function(request) {\n var pageId = getUrlParameter(\"pageId\");\n var pageVersion = getUrlParameter(\"pageVersion\");\n var macroId = getUrlParameter(\"macroId\");\n request({\n url: \"/rest/api/content/\" + pageId +\n \"/history/\" + pageVersion +\n \"/macro/id/\" + macroId,\n success: function(response) {\n var macro = JSON.parse(response);\n process(macro.body);\n }\n });\n });\n </code></pre>\n\n __Preview Mode:__ If you use the `{macro.id}` in your URL, the REST api will not return the macro body during\n a preview request, because the page has not been saved yet. You can use the `{output.type}` parameter to detect\n whether the macro is rendered in preview mode and adapt the response accordingly.\n\n __Note:__ `macro.body` will not be truncated when `renderingMethod` field was set to `POST` in static content macro.\n Refer to the [`Static Content Macros`](../static-content-macro/) for information on\n how to set this field.\n\n Currently supported variables for macros are:\n\n - `macro.hash`: The hash of the macro body (deprecated, use the macro.id)\n - `macro.id`: The id of the macro\n - `macro.body`: The macro body, truncated to 128 characters\n - `macro.truncated`: True if the macro body was truncated, false of not\n - `page.id`: The page ID, e.g. `1376295`\n - `page.title`: The page title, e.g. `My Page`\n - `page.type`: The page type, e.g. `page`\n - `page.version`: The page version, e.g. `6`\n - `space.id`: The space ID, e.g. `65537`\n - `space.key`: The space key, e.g. `AC`\n - `user.id`: The user ID, e.g. `admin` (deprecated in GDPR mode)\n - `user.key`: The user key, e.g. `ff80808143087d180143087d3a910004` (deprecated in GDPR mode)\n - `output.type`: The output type, e.g. `display` or `preview`\n\nContext parameters for macros are also required in the URL. Please see the\n [Macro Input Parameter](../macro-input-parameter/) documentation for details.\n\n"
15954
15898
  },
@@ -16158,7 +16102,6 @@
16158
16102
  "defaultValue": "false"
16159
16103
  },
16160
16104
  "url": {
16161
- "format": "uri",
16162
16105
  "type": "string",
16163
16106
  "fieldDescription": "\n\nThe URL of the add-on endpoint which will be served as a hidden iframe inside the property panel\n\n"
16164
16107
  }
@@ -16376,7 +16319,6 @@
16376
16319
  "defaultValue": "false"
16377
16320
  },
16378
16321
  "url": {
16379
- "format": "uri",
16380
16322
  "type": "string",
16381
16323
  "fieldDescription": "\n\nThe URL to the macro configuration page in the add-on.\n\n"
16382
16324
  },
@@ -16437,7 +16379,6 @@
16437
16379
  "defaultValue": "block"
16438
16380
  },
16439
16381
  "url": {
16440
- "format": "uri",
16441
16382
  "type": "string",
16442
16383
  "fieldDescription": "\n\nThe link to the add-on resource that provides the macro content.\n This URL has to be relative to the add-on base URL.\n\n Additional context parameters can be passed as variables in the URL:\n <pre><code>\n {\n \"url\": \"/macro-renderer?body={macro.body}&amp;space_id={space.id}&amp;page_id={page.id}\"\n }\n </code></pre>\n\n Since macro bodies can be of arbitrary size and may contain sensitive data, care must be taken\n as to how its passed to your connect add-on. You have three options to gain access to the body:\n\n - If you can predict the size of your body and it is consistently less than 128 characters, you\n can include it in the GET request using the `{macro.body}` parameter.\n - If you know your macro contains a body that will often exceed the 128 character threshold\n (or is known to contain sensitive data), then you can include the `{macro.id}` parameter and\n use the Confluence REST api to call back to collect the body.\n - If you want, you can include, `{macro.body}`, `{macro.id}`, and `{macro.truncated}`. This way\n your plugin can call back to confluence only if `{macro.truncated}` is '`true`'. This will allow\n you to skip the callback if it's not needed. This would be useful for macros that don't\n contain sensitive data of an unpredictable size.\n\n\n__Note:__ If you include the `{macro.body}` in your URL you are potentially leaking sensitive data\n to any intermediate host on the internet. This may result in the body being cached or indexed\n by a third party. If you are concerned about the security of your macro, you should always use\n the `{macro.id}` and use the Confluence REST API to collect the body.\n\n Here's an example:\n\n Declare the variables that are later required to fetch the macro content in the URL:\n <pre><code>\n {\n \"url\": \"/render-macro?pageId={page.id}&amp;pageVersion={page.version}&amp;macroId={macro.id}\"\n }\n </code></pre>\n\n Then use the Confluence REST API to collect the body, for example directly from the iframe:\n <pre><code>\n AP.require(\"request\", function(request) {\n var pageId = getUrlParameter(\"pageId\");\n var pageVersion = getUrlParameter(\"pageVersion\");\n var macroId = getUrlParameter(\"macroId\");\n request({\n url: \"/rest/api/content/\" + pageId +\n \"/history/\" + pageVersion +\n \"/macro/id/\" + macroId,\n success: function(response) {\n var macro = JSON.parse(response);\n process(macro.body);\n }\n });\n });\n </code></pre>\n\n __Preview Mode:__ If you use the `{macro.id}` in your URL, the REST api will not return the macro body during\n a preview request, because the page has not been saved yet. You can use the `{output.type}` parameter to detect\n whether the macro is rendered in preview mode and adapt the response accordingly.\n\n __Note:__ `macro.body` will not be truncated when `renderingMethod` field was set to `POST` in static content macro.\n Refer to the [`Static Content Macros`](../static-content-macro/) for information on\n how to set this field.\n\n Currently supported variables for macros are:\n\n - `macro.hash`: The hash of the macro body (deprecated, use the macro.id)\n - `macro.id`: The id of the macro\n - `macro.body`: The macro body, truncated to 128 characters\n - `macro.truncated`: True if the macro body was truncated, false of not\n - `page.id`: The page ID, e.g. `1376295`\n - `page.title`: The page title, e.g. `My Page`\n - `page.type`: The page type, e.g. `page`\n - `page.version`: The page version, e.g. `6`\n - `space.id`: The space ID, e.g. `65537`\n - `space.key`: The space key, e.g. `AC`\n - `user.id`: The user ID, e.g. `admin` (deprecated in GDPR mode)\n - `user.key`: The user key, e.g. `ff80808143087d180143087d3a910004` (deprecated in GDPR mode)\n - `output.type`: The output type, e.g. `display` or `preview`\n\nContext parameters for macros are also required in the URL. Please see the\n [Macro Input Parameter](../macro-input-parameter/) documentation for details.\n\n"
16443
16384
  },
@@ -16647,7 +16588,6 @@
16647
16588
  "defaultValue": "false"
16648
16589
  },
16649
16590
  "url": {
16650
- "format": "uri",
16651
16591
  "type": "string",
16652
16592
  "fieldDescription": "\n\nThe URL of the add-on endpoint which will be served as a hidden iframe inside the property panel\n\n"
16653
16593
  }
@@ -17033,7 +16973,6 @@
17033
16973
  "spaceview": {
17034
16974
  "properties": {
17035
16975
  "url": {
17036
- "format": "uri",
17037
16976
  "type": "string",
17038
16977
  "fieldDescription": "\n\nA url for displaying a given view. This url can be interpolated with a set of variables. See\n <a href=\"../theme-routes/\">Theme Routes</a> for a list of\n context parameters available.\n\n"
17039
16978
  }
@@ -17099,12 +17038,10 @@
17099
17038
  "items": {
17100
17039
  "properties": {
17101
17040
  "installed": {
17102
- "format": "uri",
17103
17041
  "type": "string",
17104
17042
  "fieldDescription": "\n\nWhen a Connect add-on is installed, a synchronous request is fired to this URL to initiate the installation\n handshake. In order to successfully complete installation, the add-on must respond with either a\n <code>200 OK</code> or <code>204 No Content</code> status.\n\n<div class=\"aui-message warning\">\n <p class=\"title\">\n <span class=\"aui-icon icon-warning\">Warning</span>\n <strong>Important</strong>\n </p>\n Upon successful registration, the add-on must return either a <code>200 OK</code> or <code>204 No Content</code>\n response code, otherwise the operation will fail and the installation will be marked as incomplete.\n</div>\n\n"
17105
17043
  },
17106
17044
  "disabled": {
17107
- "format": "uri",
17108
17045
  "type": "string",
17109
17046
  "fieldDescription": "\n\nFires when an add on has been successfully disabled. This is an asynchronous notification event.\n\n"
17110
17047
  },
@@ -17113,12 +17050,10 @@
17113
17050
  "fieldDescription": "\n\nUsed DaRe app migration service to trigger migrations events\n\n"
17114
17051
  },
17115
17052
  "uninstalled": {
17116
- "format": "uri",
17117
17053
  "type": "string",
17118
17054
  "fieldDescription": "\n\nFires when an add on has been successfully un-installed. This is an asynchronous notification event.\n\n"
17119
17055
  },
17120
17056
  "enabled": {
17121
- "format": "uri",
17122
17057
  "type": "string",
17123
17058
  "fieldDescription": "\n\nFires when an add on has been successfully enabled. This is an asynchronous notification event.\n\n"
17124
17059
  },
@@ -18574,7 +18509,6 @@
18574
18509
  "fieldDescription": "\n\nThe width in pixels of the icon image.\n\n"
18575
18510
  },
18576
18511
  "url": {
18577
- "format": "uri",
18578
18512
  "type": "string",
18579
18513
  "fieldDescription": "\n\nThe URL of the icon. Your icon needs to be hosted remotely at a web-accessible location. You can specify the\n URL as an absolute URL or relative to the add-on's base URL.\n\n"
18580
18514
  },
@@ -18770,7 +18704,6 @@
18770
18704
  "url": {
18771
18705
  "properties": {
18772
18706
  "url": {
18773
- "format": "uri",
18774
18707
  "type": "string",
18775
18708
  "fieldDescription": "\n\n"
18776
18709
  }
@@ -18789,7 +18722,6 @@
18789
18722
  "properties": {
18790
18723
  "templateUrl": {
18791
18724
  "type": "string",
18792
- "format": "uri",
18793
18725
  "fieldDescription": "\n\n"
18794
18726
  }
18795
18727
  },
@@ -18805,7 +18737,6 @@
18805
18737
  "properties": {
18806
18738
  "templateUrl": {
18807
18739
  "type": "string",
18808
- "format": "uri",
18809
18740
  "fieldDescription": ""
18810
18741
  }
18811
18742
  },
@@ -18821,7 +18752,6 @@
18821
18752
  "properties": {
18822
18753
  "templateUrl": {
18823
18754
  "type": "string",
18824
- "format": "uri",
18825
18755
  "fieldDescription": ""
18826
18756
  }
18827
18757
  },
@@ -18837,7 +18767,6 @@
18837
18767
  "properties": {
18838
18768
  "templateUrl": {
18839
18769
  "type": "string",
18840
- "format": "uri",
18841
18770
  "fieldDescription": ""
18842
18771
  }
18843
18772
  },
@@ -18858,7 +18787,6 @@
18858
18787
  "webhook": {
18859
18788
  "properties": {
18860
18789
  "url": {
18861
- "format": "uri",
18862
18790
  "type": "string"
18863
18791
  }
18864
18792
  },
@@ -18872,7 +18800,6 @@
18872
18800
  "configForm": {
18873
18801
  "properties": {
18874
18802
  "url": {
18875
- "format": "uri",
18876
18803
  "type": "string"
18877
18804
  }
18878
18805
  },
@@ -18893,7 +18820,6 @@
18893
18820
  "type": "string"
18894
18821
  },
18895
18822
  "url": {
18896
- "format": "uri",
18897
18823
  "type": "string"
18898
18824
  }
18899
18825
  },
@@ -19134,7 +19060,6 @@
19134
19060
  "embeddedStaticContentMacroBean": {
19135
19061
  "properties": {
19136
19062
  "url": {
19137
- "format": "uri",
19138
19063
  "type": "string",
19139
19064
  "fieldDescription": "\n\n"
19140
19065
  }
@@ -19226,7 +19151,6 @@
19226
19151
  "fieldDescription": "\n\nThe width in pixels of the image placeholder. Defaults to the natural image width if not specified.\n\n"
19227
19152
  },
19228
19153
  "url": {
19229
- "format": "uri",
19230
19154
  "type": "string",
19231
19155
  "fieldDescription": "\n\nThe URL of the image placeholder. Your image placeholder needs to be hosted remotely at a web-accessible location.\n You can specify the URL as an absolute URL or relative to the add-on's base URL.<br>\n\n The url here doesn't support context parameters. However all the macro parameters will be passed as query parameters to the request.<br>\n You can use these parameters to dynamically generate the placeholder image.<br>\n\n Suppose you have a macro defined like this:\n\n\n\n\n\n {\n \"dynamicContentMacros\": {\n \"renderModes\": {},\n \"url\": \"/my-macro\",\n \"categories\": [],\n \"outputType\": \"block\",\n \"bodyType\": \"none\",\n \"aliases\": [],\n \"parameters\": [\n {\n \"identifier\": \"param1\",\n \"name\": {\n \"value\": \"Parameter 1\"\n },\n \"type\": \"string\",\n \"required\": false,\n \"multiple\": false,\n \"hidden\": false\n },\n {\n \"identifier\": \"param2\",\n \"name\": {\n \"value\": \"Parameter 2\"\n },\n \"type\": \"string\",\n \"required\": false,\n \"multiple\": false,\n \"hidden\": false\n }\n ],\n \"imagePlaceholder\": {\n \"url\": \"/images/placeholder.png\",\n \"applyChrome\": false\n },\n \"name\": {\n \"value\": \"My macro with placeholder\"\n },\n \"key\": \"my-macro-key\"\n }\n }\n\n\n\n\n The Confluence editor will pass the parameter values when requesting the placeholder image:\n <code>/images/placeholder.png?param1=value1&amp;param2=value2</code>\n\n"
19232
19156
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forge/manifest",
3
- "version": "6.2.0-next.3",
3
+ "version": "6.2.0",
4
4
  "description": "Definitions and validations of the Forge manifest",
5
5
  "main": "out/index.js",
6
6
  "scripts": {
@@ -22,7 +22,7 @@
22
22
  "author": "Atlassian",
23
23
  "license": "UNLICENSED",
24
24
  "dependencies": {
25
- "@forge/util": "1.4.2-next.0",
25
+ "@forge/util": "1.4.2",
26
26
  "ajv": "^8.12.0",
27
27
  "ajv-formats": "2.1.1",
28
28
  "cheerio": "^0.22.0",