@open-resource-discovery/specification 1.14.2 → 1.14.3
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.
|
@@ -689,7 +689,7 @@
|
|
|
689
689
|
"type": "object",
|
|
690
690
|
"title": "Consumption Bundle",
|
|
691
691
|
"x-ums-type": "root",
|
|
692
|
-
"description": "A [**Consumption Bundle**](../concepts/grouping-and-bundling#consumption-bundle) groups APIs and Events together that can be consumed with the credentials and auth mechanism.\nIdeally it also includes instructions and details how to request access and credentials for resources.\n\nFor more documentation and guidance how to
|
|
692
|
+
"description": "A [**Consumption Bundle**](../concepts/grouping-and-bundling#consumption-bundle) groups APIs and Events together that can be consumed with the same credentials and auth mechanism.\nIdeally it also includes instructions and details on how to request access and credentials for resources.\n\nFor more documentation and guidance on how to use this correctly, see [Consumption Bundle](../concepts/grouping-and-bundling#consumption-bundle).\n\nA Consumption Bundle SHOULD have at least one association with a resource (0..n). Avoid empty Consumption Bundles.\nA Consumption Bundle MUST NOT contain APIs and Events that are NOT defined in the ORD document(s) returned\nby the system instance that defines the Consumption Bundle.\n\nPlease note that some ORD consumer use cases MAY depend on Consumption Bundle assignments to work with the resources.\n\nTo learn more about the concept, see [Consumption Bundle](../concepts/grouping-and-bundling#consumption-bundle).",
|
|
693
693
|
"properties": {
|
|
694
694
|
"ordId": {
|
|
695
695
|
"type": "string",
|
|
@@ -1082,6 +1082,38 @@
|
|
|
1082
1082
|
"2024.8.0"
|
|
1083
1083
|
]
|
|
1084
1084
|
},
|
|
1085
|
+
"relatedApiResources": {
|
|
1086
|
+
"type": "array",
|
|
1087
|
+
"x-introduced-in-version": "1.14.3",
|
|
1088
|
+
"description": "Optional list of related API Resources.\n\nUse this to indicate which APIs implement, expose, or are otherwise related to this entity.",
|
|
1089
|
+
"items": {
|
|
1090
|
+
"$ref": "#/definitions/RelatedApiResource"
|
|
1091
|
+
},
|
|
1092
|
+
"examples": [
|
|
1093
|
+
[
|
|
1094
|
+
{
|
|
1095
|
+
"ordId": "sap.s4:apiResource:API_BUSINESS_PARTNER:v1",
|
|
1096
|
+
"relationType": "foo.bar:relationName"
|
|
1097
|
+
}
|
|
1098
|
+
]
|
|
1099
|
+
]
|
|
1100
|
+
},
|
|
1101
|
+
"relatedEventResources": {
|
|
1102
|
+
"type": "array",
|
|
1103
|
+
"x-introduced-in-version": "1.14.3",
|
|
1104
|
+
"description": "Optional list of related Event Resources.\n\nUse this to indicate which events are emitted, consumed, or otherwise related to this entity.",
|
|
1105
|
+
"items": {
|
|
1106
|
+
"$ref": "#/definitions/RelatedEventResource"
|
|
1107
|
+
},
|
|
1108
|
+
"examples": [
|
|
1109
|
+
[
|
|
1110
|
+
{
|
|
1111
|
+
"ordId": "sap.s4:eventResource:BusinessPartnerEvents:v1",
|
|
1112
|
+
"relationType": "foo.bar:relationName"
|
|
1113
|
+
}
|
|
1114
|
+
]
|
|
1115
|
+
]
|
|
1116
|
+
},
|
|
1085
1117
|
"deprecationDate": {
|
|
1086
1118
|
"type": "string",
|
|
1087
1119
|
"format": "date-time",
|
|
@@ -1927,6 +1959,38 @@
|
|
|
1927
1959
|
"2024.8.0"
|
|
1928
1960
|
]
|
|
1929
1961
|
},
|
|
1962
|
+
"relatedApiResources": {
|
|
1963
|
+
"type": "array",
|
|
1964
|
+
"x-introduced-in-version": "1.14.3",
|
|
1965
|
+
"description": "Optional list of related API Resources.\n\nUse this to indicate which APIs implement, expose, or are otherwise related to this entity.",
|
|
1966
|
+
"items": {
|
|
1967
|
+
"$ref": "#/definitions/RelatedApiResource"
|
|
1968
|
+
},
|
|
1969
|
+
"examples": [
|
|
1970
|
+
[
|
|
1971
|
+
{
|
|
1972
|
+
"ordId": "sap.s4:apiResource:API_BUSINESS_PARTNER:v1",
|
|
1973
|
+
"relationType": "foo.bar:relationName"
|
|
1974
|
+
}
|
|
1975
|
+
]
|
|
1976
|
+
]
|
|
1977
|
+
},
|
|
1978
|
+
"relatedEventResources": {
|
|
1979
|
+
"type": "array",
|
|
1980
|
+
"x-introduced-in-version": "1.14.3",
|
|
1981
|
+
"description": "Optional list of related Event Resources.\n\nUse this to indicate which events are emitted, consumed, or otherwise related to this entity.",
|
|
1982
|
+
"items": {
|
|
1983
|
+
"$ref": "#/definitions/RelatedEventResource"
|
|
1984
|
+
},
|
|
1985
|
+
"examples": [
|
|
1986
|
+
[
|
|
1987
|
+
{
|
|
1988
|
+
"ordId": "sap.s4:eventResource:BusinessPartnerEvents:v1",
|
|
1989
|
+
"relationType": "foo.bar:relationName"
|
|
1990
|
+
}
|
|
1991
|
+
]
|
|
1992
|
+
]
|
|
1993
|
+
},
|
|
1930
1994
|
"deprecationDate": {
|
|
1931
1995
|
"type": "string",
|
|
1932
1996
|
"format": "date-time",
|
|
@@ -2403,7 +2467,7 @@
|
|
|
2403
2467
|
"type": "object",
|
|
2404
2468
|
"title": "Entity Type",
|
|
2405
2469
|
"x-ums-type": "root",
|
|
2406
|
-
"description": "An [**Entity Type**](../concepts/grouping-and-bundling#entity-type) describes either a business concept / term or an underlying conceptual model
|
|
2470
|
+
"description": "An [**Entity Type**](../concepts/grouping-and-bundling#entity-type) describes either a business concept / term or an underlying conceptual model (e.g. a business object / domain model).\nEntity Types can be related to API & Event resources, Data Products and other Entity Types, connecting exposed resources to business semantics.\n\nTo learn more about the concept, see [Entity Type](../concepts/grouping-and-bundling#entity-type).",
|
|
2407
2471
|
"x-introduced-in-version": "1.8.0",
|
|
2408
2472
|
"properties": {
|
|
2409
2473
|
"ordId": {
|
|
@@ -4347,7 +4411,7 @@
|
|
|
4347
4411
|
"type": "object",
|
|
4348
4412
|
"title": "Product",
|
|
4349
4413
|
"x-ums-type": "root",
|
|
4350
|
-
"description": "A **product
|
|
4414
|
+
"description": "A [**Product**](../concepts/grouping-and-bundling#product) in ORD is understood as a software product or service offering (whether commercial or free).\n\nIt is a high-level entity for structuring the software portfolio from a portfolio / software logistics perspective.\nWhile **system type** is a technical concept, **product** covers the portfolio and marketing view.\n\nPlease note that the ORD concept of a product is very simple on purpose.\nThere is no distinction between products and services and concepts like product versions, variants, etc.\n\nORD assumes that this is handled by specialized systems and that ORD only provides the means to correlate to them.\n\nTo learn more about the concept, see [Product](../concepts/grouping-and-bundling#product).",
|
|
4351
4415
|
"properties": {
|
|
4352
4416
|
"ordId": {
|
|
4353
4417
|
"type": "string",
|
|
@@ -4668,7 +4732,7 @@
|
|
|
4668
4732
|
"relatedApiResources": {
|
|
4669
4733
|
"type": "array",
|
|
4670
4734
|
"x-introduced-in-version": "1.14.2",
|
|
4671
|
-
"description": "Optional list of related API Resources.\n\nUse this to indicate which APIs implement, expose, or are otherwise related to this
|
|
4735
|
+
"description": "Optional list of related API Resources.\n\nUse this to indicate which APIs implement, expose, or are otherwise related to this entity.",
|
|
4672
4736
|
"items": {
|
|
4673
4737
|
"$ref": "#/definitions/RelatedApiResource"
|
|
4674
4738
|
},
|
|
@@ -4684,7 +4748,7 @@
|
|
|
4684
4748
|
"relatedEventResources": {
|
|
4685
4749
|
"type": "array",
|
|
4686
4750
|
"x-introduced-in-version": "1.14.2",
|
|
4687
|
-
"description": "Optional list of related Event Resources.\n\nUse this to indicate which events are emitted, consumed, or otherwise related to this
|
|
4751
|
+
"description": "Optional list of related Event Resources.\n\nUse this to indicate which events are emitted, consumed, or otherwise related to this entity.",
|
|
4688
4752
|
"items": {
|
|
4689
4753
|
"$ref": "#/definitions/RelatedEventResource"
|
|
4690
4754
|
},
|
|
@@ -6105,7 +6169,7 @@
|
|
|
6105
6169
|
"Labels": {
|
|
6106
6170
|
"title": "Labels",
|
|
6107
6171
|
"type": "object",
|
|
6108
|
-
"description": "Generic labels that can be applied to most ORD information.\nThey are defined as an object that may have arbitrary keys.\nThe value of a key is an array of strings.\n\nLabels can be used to attach technical information that cannot be expressed natively in ORD.\nAn ORD aggregator should allow to categorize and query information based on the labels provided.\n\nIf multiple parties rely on the existence of certain label information,\nstandardization through ORD SHOULD be preferred.\n\nAll labels attached to a `Package` will be inherited to the resources they contain.\nDuplicate labels will be merged by the ORD aggregator according to the following rules:\n* Values of the same label key will be merged.\n* Duplicate values of the same label key will be removed.",
|
|
6172
|
+
"description": "Generic key-value labels that can be applied to most ORD information.\nThey are defined as an object that may have arbitrary keys.\nThe value of a key is an array of strings.\n\nLabels can be used to attach technical information that cannot be expressed natively in ORD.\nAn ORD aggregator should allow to categorize and query information based on the labels provided.\n\nTo learn more about the concept, see [Labels](../concepts/grouping-and-bundling#labels).\n\nIf multiple parties rely on the existence of certain label information,\nstandardization through ORD SHOULD be preferred.\n\nAll labels attached to a `Package` will be inherited to the resources they contain.\nDuplicate labels will be merged by the ORD aggregator according to the following rules:\n* Values of the same label key will be merged.\n* Duplicate values of the same label key will be removed.",
|
|
6109
6173
|
"x-ums-type": "custom",
|
|
6110
6174
|
"patternProperties": {
|
|
6111
6175
|
"^[a-zA-Z0-9-_.]*$": {
|
|
@@ -170,13 +170,15 @@ export interface SystemInstance {
|
|
|
170
170
|
tags?: string[];
|
|
171
171
|
}
|
|
172
172
|
/**
|
|
173
|
-
* Generic labels that can be applied to most ORD information.
|
|
173
|
+
* Generic key-value labels that can be applied to most ORD information.
|
|
174
174
|
* They are defined as an object that may have arbitrary keys.
|
|
175
175
|
* The value of a key is an array of strings.
|
|
176
176
|
*
|
|
177
177
|
* Labels can be used to attach technical information that cannot be expressed natively in ORD.
|
|
178
178
|
* An ORD aggregator should allow to categorize and query information based on the labels provided.
|
|
179
179
|
*
|
|
180
|
+
* To learn more about the concept, see [Labels](../concepts/grouping-and-bundling#labels).
|
|
181
|
+
*
|
|
180
182
|
* If multiple parties rely on the existence of certain label information,
|
|
181
183
|
* standardization through ORD SHOULD be preferred.
|
|
182
184
|
*
|
|
@@ -477,6 +479,18 @@ export interface ApiResource {
|
|
|
477
479
|
* It MUST follow the [Semantic Versioning 2.0.0](https://semver.org/) standard.
|
|
478
480
|
*/
|
|
479
481
|
minSystemVersion?: string;
|
|
482
|
+
/**
|
|
483
|
+
* Optional list of related API Resources.
|
|
484
|
+
*
|
|
485
|
+
* Use this to indicate which APIs implement, expose, or are otherwise related to this entity.
|
|
486
|
+
*/
|
|
487
|
+
relatedApiResources?: RelatedAPIResource[];
|
|
488
|
+
/**
|
|
489
|
+
* Optional list of related Event Resources.
|
|
490
|
+
*
|
|
491
|
+
* Use this to indicate which events are emitted, consumed, or otherwise related to this entity.
|
|
492
|
+
*/
|
|
493
|
+
relatedEventResources?: RelatedEventResource[];
|
|
480
494
|
/**
|
|
481
495
|
* The deprecation date defines when the resource has been set as deprecated.
|
|
482
496
|
* This is not to be confused with the `sunsetDate` which defines when the resource will be actually sunset, aka. decommissioned / removed / archived.
|
|
@@ -719,6 +733,42 @@ export interface ConsumptionBundleReference {
|
|
|
719
733
|
*/
|
|
720
734
|
defaultEntryPoint?: string;
|
|
721
735
|
}
|
|
736
|
+
/**
|
|
737
|
+
* Defines a relation to an API Resource (via its ORD ID).
|
|
738
|
+
*/
|
|
739
|
+
export interface RelatedAPIResource {
|
|
740
|
+
/**
|
|
741
|
+
* The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.
|
|
742
|
+
*
|
|
743
|
+
* It MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.
|
|
744
|
+
*/
|
|
745
|
+
ordId: string;
|
|
746
|
+
/**
|
|
747
|
+
* Optional type of the relationship as a [Concept ID](../index.md#concept-id).
|
|
748
|
+
*
|
|
749
|
+
* Defines the semantic meaning of the relationship.
|
|
750
|
+
* If not provided, the relationship has no specific semantics ("related somehow").
|
|
751
|
+
*/
|
|
752
|
+
relationType?: string;
|
|
753
|
+
}
|
|
754
|
+
/**
|
|
755
|
+
* Defines a relation to an Event Resource (via its ORD ID).
|
|
756
|
+
*/
|
|
757
|
+
export interface RelatedEventResource {
|
|
758
|
+
/**
|
|
759
|
+
* The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.
|
|
760
|
+
*
|
|
761
|
+
* It MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.
|
|
762
|
+
*/
|
|
763
|
+
ordId: string;
|
|
764
|
+
/**
|
|
765
|
+
* Optional type of the relationship as a [Concept ID](../index.md#concept-id).
|
|
766
|
+
*
|
|
767
|
+
* Defines the semantic meaning of the relationship.
|
|
768
|
+
* If not provided, the relationship has no specific semantics ("related somehow").
|
|
769
|
+
*/
|
|
770
|
+
relationType?: string;
|
|
771
|
+
}
|
|
722
772
|
/**
|
|
723
773
|
* A changelog entry can be used to indicate changes.
|
|
724
774
|
* Usually they lead to a change of the version number or the release status.
|
|
@@ -1253,6 +1303,18 @@ export interface EventResource {
|
|
|
1253
1303
|
* It MUST follow the [Semantic Versioning 2.0.0](https://semver.org/) standard.
|
|
1254
1304
|
*/
|
|
1255
1305
|
minSystemVersion?: string;
|
|
1306
|
+
/**
|
|
1307
|
+
* Optional list of related API Resources.
|
|
1308
|
+
*
|
|
1309
|
+
* Use this to indicate which APIs implement, expose, or are otherwise related to this entity.
|
|
1310
|
+
*/
|
|
1311
|
+
relatedApiResources?: RelatedAPIResource[];
|
|
1312
|
+
/**
|
|
1313
|
+
* Optional list of related Event Resources.
|
|
1314
|
+
*
|
|
1315
|
+
* Use this to indicate which events are emitted, consumed, or otherwise related to this entity.
|
|
1316
|
+
*/
|
|
1317
|
+
relatedEventResources?: RelatedEventResource[];
|
|
1256
1318
|
/**
|
|
1257
1319
|
* The deprecation date defines when the resource has been set as deprecated.
|
|
1258
1320
|
* This is not to be confused with the `sunsetDate` which defines when the resource will be actually sunset, aka. decommissioned / removed / archived.
|
|
@@ -1509,8 +1571,8 @@ export interface EventCompatibility {
|
|
|
1509
1571
|
maxVersion: string;
|
|
1510
1572
|
}
|
|
1511
1573
|
/**
|
|
1512
|
-
* An [**Entity Type**](../concepts/grouping-and-bundling#entity-type) describes either a business concept / term or an underlying conceptual model.
|
|
1513
|
-
*
|
|
1574
|
+
* An [**Entity Type**](../concepts/grouping-and-bundling#entity-type) describes either a business concept / term or an underlying conceptual model (e.g. a business object / domain model).
|
|
1575
|
+
* Entity Types can be related to API & Event resources, Data Products and other Entity Types, connecting exposed resources to business semantics.
|
|
1514
1576
|
*
|
|
1515
1577
|
* To learn more about the concept, see [Entity Type](../concepts/grouping-and-bundling#entity-type).
|
|
1516
1578
|
*/
|
|
@@ -1927,13 +1989,13 @@ export interface Capability {
|
|
|
1927
1989
|
/**
|
|
1928
1990
|
* Optional list of related API Resources.
|
|
1929
1991
|
*
|
|
1930
|
-
* Use this to indicate which APIs implement, expose, or are otherwise related to this
|
|
1992
|
+
* Use this to indicate which APIs implement, expose, or are otherwise related to this entity.
|
|
1931
1993
|
*/
|
|
1932
1994
|
relatedApiResources?: RelatedAPIResource[];
|
|
1933
1995
|
/**
|
|
1934
1996
|
* Optional list of related Event Resources.
|
|
1935
1997
|
*
|
|
1936
|
-
* Use this to indicate which events are emitted, consumed, or otherwise related to this
|
|
1998
|
+
* Use this to indicate which events are emitted, consumed, or otherwise related to this entity.
|
|
1937
1999
|
*/
|
|
1938
2000
|
relatedEventResources?: RelatedEventResource[];
|
|
1939
2001
|
/**
|
|
@@ -1982,42 +2044,6 @@ export interface Capability {
|
|
|
1982
2044
|
*/
|
|
1983
2045
|
systemInstanceAware?: boolean;
|
|
1984
2046
|
}
|
|
1985
|
-
/**
|
|
1986
|
-
* Defines a relation to an API Resource (via its ORD ID).
|
|
1987
|
-
*/
|
|
1988
|
-
export interface RelatedAPIResource {
|
|
1989
|
-
/**
|
|
1990
|
-
* The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.
|
|
1991
|
-
*
|
|
1992
|
-
* It MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.
|
|
1993
|
-
*/
|
|
1994
|
-
ordId: string;
|
|
1995
|
-
/**
|
|
1996
|
-
* Optional type of the relationship as a [Concept ID](../index.md#concept-id).
|
|
1997
|
-
*
|
|
1998
|
-
* Defines the semantic meaning of the relationship.
|
|
1999
|
-
* If not provided, the relationship has no specific semantics ("related somehow").
|
|
2000
|
-
*/
|
|
2001
|
-
relationType?: string;
|
|
2002
|
-
}
|
|
2003
|
-
/**
|
|
2004
|
-
* Defines a relation to an Event Resource (via its ORD ID).
|
|
2005
|
-
*/
|
|
2006
|
-
export interface RelatedEventResource {
|
|
2007
|
-
/**
|
|
2008
|
-
* The ORD ID is a stable, globally unique ID for ORD resources or taxonomy.
|
|
2009
|
-
*
|
|
2010
|
-
* It MUST be a valid [ORD ID](../index.md#ord-id) of the appropriate ORD type.
|
|
2011
|
-
*/
|
|
2012
|
-
ordId: string;
|
|
2013
|
-
/**
|
|
2014
|
-
* Optional type of the relationship as a [Concept ID](../index.md#concept-id).
|
|
2015
|
-
*
|
|
2016
|
-
* Defines the semantic meaning of the relationship.
|
|
2017
|
-
* If not provided, the relationship has no specific semantics ("related somehow").
|
|
2018
|
-
*/
|
|
2019
|
-
relationType?: string;
|
|
2020
|
-
}
|
|
2021
2047
|
/**
|
|
2022
2048
|
* Defines a relation to another Capability (via its ORD ID).
|
|
2023
2049
|
*/
|
|
@@ -3089,15 +3115,17 @@ export interface Vendor {
|
|
|
3089
3115
|
documentationLabels?: DocumentationLabels;
|
|
3090
3116
|
}
|
|
3091
3117
|
/**
|
|
3092
|
-
* A **product
|
|
3118
|
+
* A [**Product**](../concepts/grouping-and-bundling#product) in ORD is understood as a software product or service offering (whether commercial or free).
|
|
3093
3119
|
*
|
|
3094
|
-
* It is a high-level entity for structuring the software portfolio from a
|
|
3095
|
-
* While **system type** is a technical concept, **product** covers the
|
|
3120
|
+
* It is a high-level entity for structuring the software portfolio from a portfolio / software logistics perspective.
|
|
3121
|
+
* While **system type** is a technical concept, **product** covers the portfolio and marketing view.
|
|
3096
3122
|
*
|
|
3097
3123
|
* Please note that the ORD concept of a product is very simple on purpose.
|
|
3098
3124
|
* There is no distinction between products and services and concepts like product versions, variants, etc.
|
|
3099
3125
|
*
|
|
3100
3126
|
* ORD assumes that this is handled by specialized systems and that ORD only provides the means to correlate to them.
|
|
3127
|
+
*
|
|
3128
|
+
* To learn more about the concept, see [Product](../concepts/grouping-and-bundling#product).
|
|
3101
3129
|
*/
|
|
3102
3130
|
export interface Product {
|
|
3103
3131
|
/**
|
|
@@ -3402,10 +3430,10 @@ export interface File {
|
|
|
3402
3430
|
[k: string]: unknown | undefined;
|
|
3403
3431
|
}
|
|
3404
3432
|
/**
|
|
3405
|
-
* A [**Consumption Bundle**](../concepts/grouping-and-bundling#consumption-bundle) groups APIs and Events together that can be consumed with the credentials and auth mechanism.
|
|
3406
|
-
* Ideally it also includes instructions and details how to request access and credentials for resources.
|
|
3433
|
+
* A [**Consumption Bundle**](../concepts/grouping-and-bundling#consumption-bundle) groups APIs and Events together that can be consumed with the same credentials and auth mechanism.
|
|
3434
|
+
* Ideally it also includes instructions and details on how to request access and credentials for resources.
|
|
3407
3435
|
*
|
|
3408
|
-
* For more documentation and guidance how to
|
|
3436
|
+
* For more documentation and guidance on how to use this correctly, see [Consumption Bundle](../concepts/grouping-and-bundling#consumption-bundle).
|
|
3409
3437
|
*
|
|
3410
3438
|
* A Consumption Bundle SHOULD have at least one association with a resource (0..n). Avoid empty Consumption Bundles.
|
|
3411
3439
|
* A Consumption Bundle MUST NOT contain APIs and Events that are NOT defined in the ORD document(s) returned
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "http://json.schemastore.org/package",
|
|
3
3
|
"name": "@open-resource-discovery/specification",
|
|
4
|
-
"version": "1.14.
|
|
4
|
+
"version": "1.14.3",
|
|
5
5
|
"description": "Open Resource Discovery (ORD) Specification",
|
|
6
6
|
"author": "SAP SE",
|
|
7
7
|
"license": "Apache-2.0",
|
|
@@ -23,19 +23,20 @@
|
|
|
23
23
|
],
|
|
24
24
|
"scripts": {
|
|
25
25
|
"docusaurus": "docusaurus",
|
|
26
|
-
"build": "npm run generate && npm run build
|
|
26
|
+
"build": "npm run generate && npm run build:ts && npm run build:docusaurus",
|
|
27
27
|
"clean": "node src/helper/clean.mjs",
|
|
28
|
-
"build
|
|
29
|
-
"build
|
|
28
|
+
"build:ts": "tsc -p ./tsconfig.json",
|
|
29
|
+
"build:docusaurus": "docusaurus build",
|
|
30
30
|
"format": "biome format --write .",
|
|
31
31
|
"lint": "biome lint .",
|
|
32
|
-
"test": "npm run build
|
|
32
|
+
"test": "npm run build:ts && node --test dist/**/*.test.js",
|
|
33
33
|
"serve": "docusaurus serve",
|
|
34
34
|
"start": "docusaurus start",
|
|
35
35
|
"deploy": "npm run build && gh-pages -d ./build",
|
|
36
36
|
"pregenerate": "npm run clean",
|
|
37
37
|
"generate": "npx @open-resource-discovery/spec-toolkit -c ./spec-toolkit.config.json",
|
|
38
|
-
"postgenerate": "ts-node ./src/helper/copyGeneratedToDestination.ts"
|
|
38
|
+
"postgenerate": "ts-node ./src/helper/copyGeneratedToDestination.ts",
|
|
39
|
+
"generate:llm-notebook": "npm run generate && ts-node ./src/helper/exportForNotebookLM.ts"
|
|
39
40
|
},
|
|
40
41
|
"devDependencies": {
|
|
41
42
|
"@biomejs/biome": "2.4.9",
|