@epistola.app/epistola-client 1.3.0 → 1.4.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 (625) hide show
  1. package/CHANGELOG.md +38 -37
  2. package/README.md +21 -15
  3. package/dist/auth/jwtSigner.d.ts +3 -0
  4. package/dist/auth/jwtSigner.d.ts.map +1 -1
  5. package/dist/auth/jwtSigner.js +3 -0
  6. package/dist/auth/jwtSigner.js.map +1 -1
  7. package/dist/generated/api/apis/AttributesApi.d.ts +88 -3
  8. package/dist/generated/api/apis/AttributesApi.d.ts.map +1 -1
  9. package/dist/generated/api/apis/AttributesApi.js +82 -42
  10. package/dist/generated/api/apis/AttributesApi.js.map +1 -1
  11. package/dist/generated/api/apis/CatalogsApi.d.ts +85 -3
  12. package/dist/generated/api/apis/CatalogsApi.d.ts.map +1 -1
  13. package/dist/generated/api/apis/CatalogsApi.js +82 -39
  14. package/dist/generated/api/apis/CatalogsApi.js.map +1 -1
  15. package/dist/generated/api/apis/CodeListsApi.d.ts +139 -3
  16. package/dist/generated/api/apis/CodeListsApi.d.ts.map +1 -1
  17. package/dist/generated/api/apis/CodeListsApi.js +130 -66
  18. package/dist/generated/api/apis/CodeListsApi.js.map +1 -1
  19. package/dist/generated/api/apis/ConsumersApi.d.ts +126 -19
  20. package/dist/generated/api/apis/ConsumersApi.d.ts.map +1 -1
  21. package/dist/generated/api/apis/ConsumersApi.js +130 -66
  22. package/dist/generated/api/apis/ConsumersApi.js.map +1 -1
  23. package/dist/generated/api/apis/ContractsApi.d.ts +66 -3
  24. package/dist/generated/api/apis/ContractsApi.d.ts.map +1 -1
  25. package/dist/generated/api/apis/ContractsApi.js +71 -35
  26. package/dist/generated/api/apis/ContractsApi.js.map +1 -1
  27. package/dist/generated/api/apis/EnvironmentsApi.d.ts +73 -3
  28. package/dist/generated/api/apis/EnvironmentsApi.d.ts.map +1 -1
  29. package/dist/generated/api/apis/EnvironmentsApi.js +77 -37
  30. package/dist/generated/api/apis/EnvironmentsApi.js.map +1 -1
  31. package/dist/generated/api/apis/FontsApi.d.ts +44 -3
  32. package/dist/generated/api/apis/FontsApi.d.ts.map +1 -1
  33. package/dist/generated/api/apis/FontsApi.js +35 -18
  34. package/dist/generated/api/apis/FontsApi.js.map +1 -1
  35. package/dist/generated/api/apis/GenerationApi.d.ts +128 -3
  36. package/dist/generated/api/apis/GenerationApi.d.ts.map +1 -1
  37. package/dist/generated/api/apis/GenerationApi.js +148 -68
  38. package/dist/generated/api/apis/GenerationApi.js.map +1 -1
  39. package/dist/generated/api/apis/ImagesApi.d.ts +74 -3
  40. package/dist/generated/api/apis/ImagesApi.d.ts.map +1 -1
  41. package/dist/generated/api/apis/ImagesApi.js +64 -33
  42. package/dist/generated/api/apis/ImagesApi.js.map +1 -1
  43. package/dist/generated/api/apis/StencilsApi.d.ts +283 -3
  44. package/dist/generated/api/apis/StencilsApi.d.ts.map +1 -1
  45. package/dist/generated/api/apis/StencilsApi.js +234 -123
  46. package/dist/generated/api/apis/StencilsApi.js.map +1 -1
  47. package/dist/generated/api/apis/SystemApi.d.ts +11 -3
  48. package/dist/generated/api/apis/SystemApi.d.ts.map +1 -1
  49. package/dist/generated/api/apis/SystemApi.js +16 -8
  50. package/dist/generated/api/apis/SystemApi.js.map +1 -1
  51. package/dist/generated/api/apis/TemplatesApi.d.ts +111 -5
  52. package/dist/generated/api/apis/TemplatesApi.d.ts.map +1 -1
  53. package/dist/generated/api/apis/TemplatesApi.js +101 -51
  54. package/dist/generated/api/apis/TemplatesApi.js.map +1 -1
  55. package/dist/generated/api/apis/TenantsApi.d.ts +61 -3
  56. package/dist/generated/api/apis/TenantsApi.d.ts.map +1 -1
  57. package/dist/generated/api/apis/TenantsApi.js +72 -32
  58. package/dist/generated/api/apis/TenantsApi.js.map +1 -1
  59. package/dist/generated/api/apis/ThemesApi.d.ts +91 -3
  60. package/dist/generated/api/apis/ThemesApi.d.ts.map +1 -1
  61. package/dist/generated/api/apis/ThemesApi.js +82 -42
  62. package/dist/generated/api/apis/ThemesApi.js.map +1 -1
  63. package/dist/generated/api/apis/VariantsApi.d.ts +259 -3
  64. package/dist/generated/api/apis/VariantsApi.d.ts.map +1 -1
  65. package/dist/generated/api/apis/VariantsApi.js +235 -129
  66. package/dist/generated/api/apis/VariantsApi.js.map +1 -1
  67. package/dist/generated/api/apis/VersionsApi.d.ts +124 -3
  68. package/dist/generated/api/apis/VersionsApi.d.ts.map +1 -1
  69. package/dist/generated/api/apis/VersionsApi.js +94 -54
  70. package/dist/generated/api/apis/VersionsApi.js.map +1 -1
  71. package/dist/generated/api/models/ActivationDto.d.ts +2 -10
  72. package/dist/generated/api/models/ActivationDto.d.ts.map +1 -1
  73. package/dist/generated/api/models/ActivationDto.js +5 -5
  74. package/dist/generated/api/models/ActivationDto.js.map +1 -1
  75. package/dist/generated/api/models/ActivationListResponse.d.ts +2 -4
  76. package/dist/generated/api/models/ActivationListResponse.d.ts.map +1 -1
  77. package/dist/generated/api/models/ActivationListResponse.js +2 -2
  78. package/dist/generated/api/models/ActivationListResponse.js.map +1 -1
  79. package/dist/generated/api/models/ApplyStencilUpgradeRequest.d.ts +2 -10
  80. package/dist/generated/api/models/ApplyStencilUpgradeRequest.d.ts.map +1 -1
  81. package/dist/generated/api/models/ApplyStencilUpgradeRequest.js +2 -2
  82. package/dist/generated/api/models/ApplyStencilUpgradeRequest.js.map +1 -1
  83. package/dist/generated/api/models/ApplyStencilUpgradeResponse.d.ts +2 -10
  84. package/dist/generated/api/models/ApplyStencilUpgradeResponse.d.ts.map +1 -1
  85. package/dist/generated/api/models/ApplyStencilUpgradeResponse.js +2 -2
  86. package/dist/generated/api/models/ApplyStencilUpgradeResponse.js.map +1 -1
  87. package/dist/generated/api/models/ApproveConsumerRequest.d.ts +2 -6
  88. package/dist/generated/api/models/ApproveConsumerRequest.d.ts.map +1 -1
  89. package/dist/generated/api/models/ApproveConsumerRequest.js +5 -5
  90. package/dist/generated/api/models/ApproveConsumerRequest.js.map +1 -1
  91. package/dist/generated/api/models/AttributeDto.d.ts +10 -28
  92. package/dist/generated/api/models/AttributeDto.d.ts.map +1 -1
  93. package/dist/generated/api/models/AttributeDto.js +11 -13
  94. package/dist/generated/api/models/AttributeDto.js.map +1 -1
  95. package/dist/generated/api/models/AttributeDtoCodeListBinding.d.ts +2 -6
  96. package/dist/generated/api/models/AttributeDtoCodeListBinding.d.ts.map +1 -1
  97. package/dist/generated/api/models/AttributeDtoCodeListBinding.js +2 -2
  98. package/dist/generated/api/models/AttributeDtoCodeListBinding.js.map +1 -1
  99. package/dist/generated/api/models/AttributeListResponse.d.ts +2 -6
  100. package/dist/generated/api/models/AttributeListResponse.d.ts.map +1 -1
  101. package/dist/generated/api/models/AttributeListResponse.js +2 -2
  102. package/dist/generated/api/models/AttributeListResponse.js.map +1 -1
  103. package/dist/generated/api/models/BatchGenerationItem.d.ts +2 -22
  104. package/dist/generated/api/models/BatchGenerationItem.d.ts.map +1 -1
  105. package/dist/generated/api/models/BatchGenerationItem.js +8 -8
  106. package/dist/generated/api/models/BatchGenerationItem.js.map +1 -1
  107. package/dist/generated/api/models/BlockStylePreset.d.ts +2 -8
  108. package/dist/generated/api/models/BlockStylePreset.d.ts.map +1 -1
  109. package/dist/generated/api/models/BlockStylePreset.js +2 -2
  110. package/dist/generated/api/models/BlockStylePreset.js.map +1 -1
  111. package/dist/generated/api/models/CatalogDto.d.ts +9 -17
  112. package/dist/generated/api/models/CatalogDto.d.ts.map +1 -1
  113. package/dist/generated/api/models/CatalogDto.js +7 -9
  114. package/dist/generated/api/models/CatalogDto.js.map +1 -1
  115. package/dist/generated/api/models/CatalogInstallResultDto.d.ts +2 -10
  116. package/dist/generated/api/models/CatalogInstallResultDto.d.ts.map +1 -1
  117. package/dist/generated/api/models/CatalogInstallResultDto.js +4 -4
  118. package/dist/generated/api/models/CatalogInstallResultDto.js.map +1 -1
  119. package/dist/generated/api/models/CatalogListResponse.d.ts +2 -6
  120. package/dist/generated/api/models/CatalogListResponse.d.ts.map +1 -1
  121. package/dist/generated/api/models/CatalogListResponse.js +2 -2
  122. package/dist/generated/api/models/CatalogListResponse.js.map +1 -1
  123. package/dist/generated/api/models/CatalogUpgradeDiff.d.ts +2 -22
  124. package/dist/generated/api/models/CatalogUpgradeDiff.d.ts.map +1 -1
  125. package/dist/generated/api/models/CatalogUpgradeDiff.js +3 -3
  126. package/dist/generated/api/models/CatalogUpgradeDiff.js.map +1 -1
  127. package/dist/generated/api/models/CodeListDto.d.ts +2 -30
  128. package/dist/generated/api/models/CodeListDto.d.ts.map +1 -1
  129. package/dist/generated/api/models/CodeListDto.js +15 -15
  130. package/dist/generated/api/models/CodeListDto.js.map +1 -1
  131. package/dist/generated/api/models/CodeListEntriesResponse.d.ts +2 -4
  132. package/dist/generated/api/models/CodeListEntriesResponse.d.ts.map +1 -1
  133. package/dist/generated/api/models/CodeListEntriesResponse.js +2 -2
  134. package/dist/generated/api/models/CodeListEntriesResponse.js.map +1 -1
  135. package/dist/generated/api/models/CodeListEntryDto.d.ts +2 -10
  136. package/dist/generated/api/models/CodeListEntryDto.d.ts.map +1 -1
  137. package/dist/generated/api/models/CodeListEntryDto.js +2 -2
  138. package/dist/generated/api/models/CodeListEntryDto.js.map +1 -1
  139. package/dist/generated/api/models/CodeListListResponse.d.ts +2 -6
  140. package/dist/generated/api/models/CodeListListResponse.d.ts.map +1 -1
  141. package/dist/generated/api/models/CodeListListResponse.js +2 -2
  142. package/dist/generated/api/models/CodeListListResponse.js.map +1 -1
  143. package/dist/generated/api/models/CollectMeta.d.ts +2 -12
  144. package/dist/generated/api/models/CollectMeta.d.ts.map +1 -1
  145. package/dist/generated/api/models/CollectMeta.js +3 -3
  146. package/dist/generated/api/models/CollectMeta.js.map +1 -1
  147. package/dist/generated/api/models/CollectRequest.d.ts +2 -6
  148. package/dist/generated/api/models/CollectRequest.d.ts.map +1 -1
  149. package/dist/generated/api/models/CollectRequest.js +3 -3
  150. package/dist/generated/api/models/CollectRequest.js.map +1 -1
  151. package/dist/generated/api/models/ConsumerDto.d.ts +12 -43
  152. package/dist/generated/api/models/ConsumerDto.d.ts.map +1 -1
  153. package/dist/generated/api/models/ConsumerDto.js +18 -18
  154. package/dist/generated/api/models/ConsumerDto.js.map +1 -1
  155. package/dist/generated/api/models/ConsumerListResponse.d.ts +2 -6
  156. package/dist/generated/api/models/ConsumerListResponse.d.ts.map +1 -1
  157. package/dist/generated/api/models/ConsumerListResponse.js +2 -2
  158. package/dist/generated/api/models/ConsumerListResponse.js.map +1 -1
  159. package/dist/generated/api/models/ConsumerNodeDto.d.ts +2 -10
  160. package/dist/generated/api/models/ConsumerNodeDto.d.ts.map +1 -1
  161. package/dist/generated/api/models/ConsumerNodeDto.js +6 -6
  162. package/dist/generated/api/models/ConsumerNodeDto.js.map +1 -1
  163. package/dist/generated/api/models/ConsumerPermissions.d.ts +2 -20
  164. package/dist/generated/api/models/ConsumerPermissions.d.ts.map +1 -1
  165. package/dist/generated/api/models/ConsumerPermissions.js +11 -11
  166. package/dist/generated/api/models/ConsumerPermissions.js.map +1 -1
  167. package/dist/generated/api/models/ContractBreakingChangeDto.d.ts +2 -8
  168. package/dist/generated/api/models/ContractBreakingChangeDto.d.ts.map +1 -1
  169. package/dist/generated/api/models/ContractBreakingChangeDto.js +3 -3
  170. package/dist/generated/api/models/ContractBreakingChangeDto.js.map +1 -1
  171. package/dist/generated/api/models/ContractVersionListResponse.d.ts +2 -4
  172. package/dist/generated/api/models/ContractVersionListResponse.d.ts.map +1 -1
  173. package/dist/generated/api/models/ContractVersionListResponse.js +2 -2
  174. package/dist/generated/api/models/ContractVersionListResponse.js.map +1 -1
  175. package/dist/generated/api/models/ContractVersionSummaryDto.d.ts +2 -10
  176. package/dist/generated/api/models/ContractVersionSummaryDto.d.ts.map +1 -1
  177. package/dist/generated/api/models/ContractVersionSummaryDto.js +8 -8
  178. package/dist/generated/api/models/ContractVersionSummaryDto.js.map +1 -1
  179. package/dist/generated/api/models/CreateAttributeRequest.d.ts +3 -13
  180. package/dist/generated/api/models/CreateAttributeRequest.d.ts.map +1 -1
  181. package/dist/generated/api/models/CreateAttributeRequest.js +4 -4
  182. package/dist/generated/api/models/CreateAttributeRequest.js.map +1 -1
  183. package/dist/generated/api/models/CreateAttributeRequestCodeListBinding.d.ts +2 -6
  184. package/dist/generated/api/models/CreateAttributeRequestCodeListBinding.d.ts.map +1 -1
  185. package/dist/generated/api/models/CreateAttributeRequestCodeListBinding.js +2 -2
  186. package/dist/generated/api/models/CreateAttributeRequestCodeListBinding.js.map +1 -1
  187. package/dist/generated/api/models/CreateCodeListRequest.d.ts +2 -18
  188. package/dist/generated/api/models/CreateCodeListRequest.d.ts.map +1 -1
  189. package/dist/generated/api/models/CreateCodeListRequest.js +7 -7
  190. package/dist/generated/api/models/CreateCodeListRequest.js.map +1 -1
  191. package/dist/generated/api/models/CreateContractDraftResponse.d.ts +2 -6
  192. package/dist/generated/api/models/CreateContractDraftResponse.d.ts.map +1 -1
  193. package/dist/generated/api/models/CreateContractDraftResponse.js +5 -3
  194. package/dist/generated/api/models/CreateContractDraftResponse.js.map +1 -1
  195. package/dist/generated/api/models/CreateEnvironmentRequest.d.ts +2 -6
  196. package/dist/generated/api/models/CreateEnvironmentRequest.d.ts.map +1 -1
  197. package/dist/generated/api/models/CreateEnvironmentRequest.js +2 -2
  198. package/dist/generated/api/models/CreateEnvironmentRequest.js.map +1 -1
  199. package/dist/generated/api/models/CreateStencilRequest.d.ts +2 -14
  200. package/dist/generated/api/models/CreateStencilRequest.d.ts.map +1 -1
  201. package/dist/generated/api/models/CreateStencilRequest.js +3 -3
  202. package/dist/generated/api/models/CreateStencilRequest.js.map +1 -1
  203. package/dist/generated/api/models/CreateStencilVersionRequest.d.ts +2 -6
  204. package/dist/generated/api/models/CreateStencilVersionRequest.d.ts.map +1 -1
  205. package/dist/generated/api/models/CreateStencilVersionRequest.js +3 -3
  206. package/dist/generated/api/models/CreateStencilVersionRequest.js.map +1 -1
  207. package/dist/generated/api/models/CreateTemplateRequest.d.ts +2 -8
  208. package/dist/generated/api/models/CreateTemplateRequest.d.ts.map +1 -1
  209. package/dist/generated/api/models/CreateTemplateRequest.js +2 -2
  210. package/dist/generated/api/models/CreateTemplateRequest.js.map +1 -1
  211. package/dist/generated/api/models/CreateTenantRequest.d.ts +2 -6
  212. package/dist/generated/api/models/CreateTenantRequest.d.ts.map +1 -1
  213. package/dist/generated/api/models/CreateTenantRequest.js +2 -2
  214. package/dist/generated/api/models/CreateTenantRequest.js.map +1 -1
  215. package/dist/generated/api/models/CreateThemeRequest.d.ts +2 -16
  216. package/dist/generated/api/models/CreateThemeRequest.d.ts.map +1 -1
  217. package/dist/generated/api/models/CreateThemeRequest.js +2 -2
  218. package/dist/generated/api/models/CreateThemeRequest.js.map +1 -1
  219. package/dist/generated/api/models/CreateVariantRequest.d.ts +2 -10
  220. package/dist/generated/api/models/CreateVariantRequest.d.ts.map +1 -1
  221. package/dist/generated/api/models/CreateVariantRequest.js +3 -3
  222. package/dist/generated/api/models/CreateVariantRequest.js.map +1 -1
  223. package/dist/generated/api/models/DataExampleDto.d.ts +2 -8
  224. package/dist/generated/api/models/DataExampleDto.d.ts.map +1 -1
  225. package/dist/generated/api/models/DataExampleDto.js +2 -2
  226. package/dist/generated/api/models/DataExampleDto.js.map +1 -1
  227. package/dist/generated/api/models/DataModelValidationError.d.ts +2 -6
  228. package/dist/generated/api/models/DataModelValidationError.d.ts.map +1 -1
  229. package/dist/generated/api/models/DataModelValidationError.js +2 -2
  230. package/dist/generated/api/models/DataModelValidationError.js.map +1 -1
  231. package/dist/generated/api/models/DataModelValidationProblemDetail.d.ts +2 -14
  232. package/dist/generated/api/models/DataModelValidationProblemDetail.d.ts.map +1 -1
  233. package/dist/generated/api/models/DataModelValidationProblemDetail.js +2 -2
  234. package/dist/generated/api/models/DataModelValidationProblemDetail.js.map +1 -1
  235. package/dist/generated/api/models/DocumentDto.d.ts +2 -24
  236. package/dist/generated/api/models/DocumentDto.d.ts.map +1 -1
  237. package/dist/generated/api/models/DocumentDto.js +7 -7
  238. package/dist/generated/api/models/DocumentDto.js.map +1 -1
  239. package/dist/generated/api/models/DocumentGenerationItemDto.d.ts +2 -30
  240. package/dist/generated/api/models/DocumentGenerationItemDto.d.ts.map +1 -1
  241. package/dist/generated/api/models/DocumentGenerationItemDto.js +16 -16
  242. package/dist/generated/api/models/DocumentGenerationItemDto.js.map +1 -1
  243. package/dist/generated/api/models/DocumentGenerationJobDto.d.ts +2 -24
  244. package/dist/generated/api/models/DocumentGenerationJobDto.d.ts.map +1 -1
  245. package/dist/generated/api/models/DocumentGenerationJobDto.js +12 -12
  246. package/dist/generated/api/models/DocumentGenerationJobDto.js.map +1 -1
  247. package/dist/generated/api/models/DocumentListResponse.d.ts +2 -6
  248. package/dist/generated/api/models/DocumentListResponse.d.ts.map +1 -1
  249. package/dist/generated/api/models/DocumentListResponse.js +2 -2
  250. package/dist/generated/api/models/DocumentListResponse.js.map +1 -1
  251. package/dist/generated/api/models/DroppedStencilFillDto.d.ts +2 -6
  252. package/dist/generated/api/models/DroppedStencilFillDto.d.ts.map +1 -1
  253. package/dist/generated/api/models/DroppedStencilFillDto.js +2 -2
  254. package/dist/generated/api/models/DroppedStencilFillDto.js.map +1 -1
  255. package/dist/generated/api/models/EnvironmentDto.d.ts +9 -13
  256. package/dist/generated/api/models/EnvironmentDto.d.ts.map +1 -1
  257. package/dist/generated/api/models/EnvironmentDto.js +6 -8
  258. package/dist/generated/api/models/EnvironmentDto.js.map +1 -1
  259. package/dist/generated/api/models/EnvironmentListResponse.d.ts +2 -6
  260. package/dist/generated/api/models/EnvironmentListResponse.d.ts.map +1 -1
  261. package/dist/generated/api/models/EnvironmentListResponse.js +2 -2
  262. package/dist/generated/api/models/EnvironmentListResponse.js.map +1 -1
  263. package/dist/generated/api/models/FontDto.d.ts +2 -20
  264. package/dist/generated/api/models/FontDto.d.ts.map +1 -1
  265. package/dist/generated/api/models/FontDto.js +9 -9
  266. package/dist/generated/api/models/FontDto.js.map +1 -1
  267. package/dist/generated/api/models/FontListResponse.d.ts +2 -6
  268. package/dist/generated/api/models/FontListResponse.d.ts.map +1 -1
  269. package/dist/generated/api/models/FontListResponse.js +2 -2
  270. package/dist/generated/api/models/FontListResponse.js.map +1 -1
  271. package/dist/generated/api/models/FontVariantDto.d.ts +2 -6
  272. package/dist/generated/api/models/FontVariantDto.d.ts.map +1 -1
  273. package/dist/generated/api/models/FontVariantDto.js +2 -2
  274. package/dist/generated/api/models/FontVariantDto.js.map +1 -1
  275. package/dist/generated/api/models/GenerateBatchRequest.d.ts +2 -6
  276. package/dist/generated/api/models/GenerateBatchRequest.d.ts.map +1 -1
  277. package/dist/generated/api/models/GenerateBatchRequest.js +3 -3
  278. package/dist/generated/api/models/GenerateBatchRequest.js.map +1 -1
  279. package/dist/generated/api/models/GenerateDocumentRequest.d.ts +2 -22
  280. package/dist/generated/api/models/GenerateDocumentRequest.d.ts.map +1 -1
  281. package/dist/generated/api/models/GenerateDocumentRequest.js +8 -8
  282. package/dist/generated/api/models/GenerateDocumentRequest.js.map +1 -1
  283. package/dist/generated/api/models/GenerationJobDetail.d.ts +2 -6
  284. package/dist/generated/api/models/GenerationJobDetail.d.ts.map +1 -1
  285. package/dist/generated/api/models/GenerationJobDetail.js +2 -2
  286. package/dist/generated/api/models/GenerationJobDetail.js.map +1 -1
  287. package/dist/generated/api/models/GenerationJobListResponse.d.ts +2 -6
  288. package/dist/generated/api/models/GenerationJobListResponse.d.ts.map +1 -1
  289. package/dist/generated/api/models/GenerationJobListResponse.js +2 -2
  290. package/dist/generated/api/models/GenerationJobListResponse.js.map +1 -1
  291. package/dist/generated/api/models/GenerationJobResponse.d.ts +2 -12
  292. package/dist/generated/api/models/GenerationJobResponse.d.ts.map +1 -1
  293. package/dist/generated/api/models/GenerationJobResponse.js +7 -7
  294. package/dist/generated/api/models/GenerationJobResponse.js.map +1 -1
  295. package/dist/generated/api/models/GenerationResult.d.ts +2 -32
  296. package/dist/generated/api/models/GenerationResult.d.ts.map +1 -1
  297. package/dist/generated/api/models/GenerationResult.js +16 -16
  298. package/dist/generated/api/models/GenerationResult.js.map +1 -1
  299. package/dist/generated/api/models/ImageDto.d.ts +2 -24
  300. package/dist/generated/api/models/ImageDto.d.ts.map +1 -1
  301. package/dist/generated/api/models/ImageDto.js +8 -8
  302. package/dist/generated/api/models/ImageDto.js.map +1 -1
  303. package/dist/generated/api/models/ImageListResponse.d.ts +2 -6
  304. package/dist/generated/api/models/ImageListResponse.d.ts.map +1 -1
  305. package/dist/generated/api/models/ImageListResponse.js +2 -2
  306. package/dist/generated/api/models/ImageListResponse.js.map +1 -1
  307. package/dist/generated/api/models/ImportCatalogResponse.d.ts +2 -16
  308. package/dist/generated/api/models/ImportCatalogResponse.d.ts.map +1 -1
  309. package/dist/generated/api/models/ImportCatalogResponse.js +2 -2
  310. package/dist/generated/api/models/ImportCatalogResponse.js.map +1 -1
  311. package/dist/generated/api/models/ImportTemplateResultDto.d.ts +2 -12
  312. package/dist/generated/api/models/ImportTemplateResultDto.d.ts.map +1 -1
  313. package/dist/generated/api/models/ImportTemplateResultDto.js +4 -4
  314. package/dist/generated/api/models/ImportTemplateResultDto.js.map +1 -1
  315. package/dist/generated/api/models/IncompatibleTemplateVersionDto.d.ts +2 -8
  316. package/dist/generated/api/models/IncompatibleTemplateVersionDto.d.ts.map +1 -1
  317. package/dist/generated/api/models/IncompatibleTemplateVersionDto.js +2 -2
  318. package/dist/generated/api/models/IncompatibleTemplateVersionDto.js.map +1 -1
  319. package/dist/generated/api/models/InvalidDataField.d.ts +45 -0
  320. package/dist/generated/api/models/InvalidDataField.d.ts.map +1 -0
  321. package/dist/generated/api/models/InvalidDataField.js +55 -0
  322. package/dist/generated/api/models/InvalidDataField.js.map +1 -0
  323. package/dist/generated/api/models/Margins.d.ts +2 -10
  324. package/dist/generated/api/models/Margins.d.ts.map +1 -1
  325. package/dist/generated/api/models/Margins.js +2 -2
  326. package/dist/generated/api/models/Margins.js.map +1 -1
  327. package/dist/generated/api/models/MissingDataField.d.ts +41 -0
  328. package/dist/generated/api/models/MissingDataField.d.ts.map +1 -0
  329. package/dist/generated/api/models/MissingDataField.js +53 -0
  330. package/dist/generated/api/models/MissingDataField.js.map +1 -0
  331. package/dist/generated/api/models/Node.d.ts +2 -14
  332. package/dist/generated/api/models/Node.d.ts.map +1 -1
  333. package/dist/generated/api/models/Node.js +2 -2
  334. package/dist/generated/api/models/Node.js.map +1 -1
  335. package/dist/generated/api/models/Orientation.d.ts +2 -2
  336. package/dist/generated/api/models/Orientation.js +3 -3
  337. package/dist/generated/api/models/PageFormat.d.ts +2 -2
  338. package/dist/generated/api/models/PageFormat.js +3 -3
  339. package/dist/generated/api/models/PageMeta.d.ts +2 -10
  340. package/dist/generated/api/models/PageMeta.d.ts.map +1 -1
  341. package/dist/generated/api/models/PageMeta.js +2 -2
  342. package/dist/generated/api/models/PageMeta.js.map +1 -1
  343. package/dist/generated/api/models/PageSettings.d.ts +2 -10
  344. package/dist/generated/api/models/PageSettings.d.ts.map +1 -1
  345. package/dist/generated/api/models/PageSettings.js +2 -2
  346. package/dist/generated/api/models/PageSettings.js.map +1 -1
  347. package/dist/generated/api/models/PartitionAssignment.d.ts +2 -8
  348. package/dist/generated/api/models/PartitionAssignment.d.ts.map +1 -1
  349. package/dist/generated/api/models/PartitionAssignment.js +5 -3
  350. package/dist/generated/api/models/PartitionAssignment.js.map +1 -1
  351. package/dist/generated/api/models/PingRequest.d.ts +2 -8
  352. package/dist/generated/api/models/PingRequest.d.ts.map +1 -1
  353. package/dist/generated/api/models/PingRequest.js +2 -2
  354. package/dist/generated/api/models/PingRequest.js.map +1 -1
  355. package/dist/generated/api/models/PongDetailsDto.d.ts +2 -10
  356. package/dist/generated/api/models/PongDetailsDto.d.ts.map +1 -1
  357. package/dist/generated/api/models/PongDetailsDto.js +2 -2
  358. package/dist/generated/api/models/PongDetailsDto.js.map +1 -1
  359. package/dist/generated/api/models/PongResponse.d.ts +2 -8
  360. package/dist/generated/api/models/PongResponse.d.ts.map +1 -1
  361. package/dist/generated/api/models/PongResponse.js +6 -6
  362. package/dist/generated/api/models/PongResponse.js.map +1 -1
  363. package/dist/generated/api/models/PreviewDocumentRequest.d.ts +2 -16
  364. package/dist/generated/api/models/PreviewDocumentRequest.d.ts.map +1 -1
  365. package/dist/generated/api/models/PreviewDocumentRequest.js +5 -5
  366. package/dist/generated/api/models/PreviewDocumentRequest.js.map +1 -1
  367. package/dist/generated/api/models/ProblemDetail.d.ts +2 -12
  368. package/dist/generated/api/models/ProblemDetail.d.ts.map +1 -1
  369. package/dist/generated/api/models/ProblemDetail.js +2 -2
  370. package/dist/generated/api/models/ProblemDetail.js.map +1 -1
  371. package/dist/generated/api/models/PublishContractRequest.d.ts +2 -4
  372. package/dist/generated/api/models/PublishContractRequest.d.ts.map +1 -1
  373. package/dist/generated/api/models/PublishContractRequest.js +2 -2
  374. package/dist/generated/api/models/PublishContractRequest.js.map +1 -1
  375. package/dist/generated/api/models/PublishContractResponse.d.ts +2 -10
  376. package/dist/generated/api/models/PublishContractResponse.d.ts.map +1 -1
  377. package/dist/generated/api/models/PublishContractResponse.js +2 -2
  378. package/dist/generated/api/models/PublishContractResponse.js.map +1 -1
  379. package/dist/generated/api/models/PublishVersionRequest.d.ts +2 -4
  380. package/dist/generated/api/models/PublishVersionRequest.d.ts.map +1 -1
  381. package/dist/generated/api/models/PublishVersionRequest.js +2 -2
  382. package/dist/generated/api/models/PublishVersionRequest.js.map +1 -1
  383. package/dist/generated/api/models/RegisterConsumerRequest.d.ts +2 -14
  384. package/dist/generated/api/models/RegisterConsumerRequest.d.ts.map +1 -1
  385. package/dist/generated/api/models/RegisterConsumerRequest.js +2 -2
  386. package/dist/generated/api/models/RegisterConsumerRequest.js.map +1 -1
  387. package/dist/generated/api/models/RejectConsumerRequest.d.ts +2 -4
  388. package/dist/generated/api/models/RejectConsumerRequest.d.ts.map +1 -1
  389. package/dist/generated/api/models/RejectConsumerRequest.js +2 -2
  390. package/dist/generated/api/models/RejectConsumerRequest.js.map +1 -1
  391. package/dist/generated/api/models/ReleaseCatalogRequest.d.ts +2 -6
  392. package/dist/generated/api/models/ReleaseCatalogRequest.d.ts.map +1 -1
  393. package/dist/generated/api/models/ReleaseCatalogRequest.js +3 -3
  394. package/dist/generated/api/models/ReleaseCatalogRequest.js.map +1 -1
  395. package/dist/generated/api/models/ReleaseCatalogResponse.d.ts +2 -12
  396. package/dist/generated/api/models/ReleaseCatalogResponse.d.ts.map +1 -1
  397. package/dist/generated/api/models/ReleaseCatalogResponse.js +6 -6
  398. package/dist/generated/api/models/ReleaseCatalogResponse.js.map +1 -1
  399. package/dist/generated/api/models/RemovedCatalogResourceDto.d.ts +2 -6
  400. package/dist/generated/api/models/RemovedCatalogResourceDto.d.ts.map +1 -1
  401. package/dist/generated/api/models/RemovedCatalogResourceDto.js +2 -2
  402. package/dist/generated/api/models/RemovedCatalogResourceDto.js.map +1 -1
  403. package/dist/generated/api/models/RotatePublicKeyRequest.d.ts +2 -4
  404. package/dist/generated/api/models/RotatePublicKeyRequest.d.ts.map +1 -1
  405. package/dist/generated/api/models/RotatePublicKeyRequest.js +2 -2
  406. package/dist/generated/api/models/RotatePublicKeyRequest.js.map +1 -1
  407. package/dist/generated/api/models/Slot.d.ts +2 -10
  408. package/dist/generated/api/models/Slot.d.ts.map +1 -1
  409. package/dist/generated/api/models/Slot.js +2 -2
  410. package/dist/generated/api/models/Slot.js.map +1 -1
  411. package/dist/generated/api/models/StencilDto.d.ts +9 -21
  412. package/dist/generated/api/models/StencilDto.d.ts.map +1 -1
  413. package/dist/generated/api/models/StencilDto.js +9 -11
  414. package/dist/generated/api/models/StencilDto.js.map +1 -1
  415. package/dist/generated/api/models/StencilListResponse.d.ts +2 -6
  416. package/dist/generated/api/models/StencilListResponse.d.ts.map +1 -1
  417. package/dist/generated/api/models/StencilListResponse.js +2 -2
  418. package/dist/generated/api/models/StencilListResponse.js.map +1 -1
  419. package/dist/generated/api/models/StencilSummaryDto.d.ts +9 -21
  420. package/dist/generated/api/models/StencilSummaryDto.d.ts.map +1 -1
  421. package/dist/generated/api/models/StencilSummaryDto.js +9 -11
  422. package/dist/generated/api/models/StencilSummaryDto.js.map +1 -1
  423. package/dist/generated/api/models/StencilUsageDto.d.ts +2 -12
  424. package/dist/generated/api/models/StencilUsageDto.d.ts.map +1 -1
  425. package/dist/generated/api/models/StencilUsageDto.js +2 -2
  426. package/dist/generated/api/models/StencilUsageDto.js.map +1 -1
  427. package/dist/generated/api/models/StencilUsageListResponse.d.ts +2 -6
  428. package/dist/generated/api/models/StencilUsageListResponse.d.ts.map +1 -1
  429. package/dist/generated/api/models/StencilUsageListResponse.js +2 -2
  430. package/dist/generated/api/models/StencilUsageListResponse.js.map +1 -1
  431. package/dist/generated/api/models/StencilVersionDto.d.ts +2 -18
  432. package/dist/generated/api/models/StencilVersionDto.d.ts.map +1 -1
  433. package/dist/generated/api/models/StencilVersionDto.js +11 -11
  434. package/dist/generated/api/models/StencilVersionDto.js.map +1 -1
  435. package/dist/generated/api/models/StencilVersionListResponse.d.ts +2 -6
  436. package/dist/generated/api/models/StencilVersionListResponse.d.ts.map +1 -1
  437. package/dist/generated/api/models/StencilVersionListResponse.js +2 -2
  438. package/dist/generated/api/models/StencilVersionListResponse.js.map +1 -1
  439. package/dist/generated/api/models/StencilVersionSummaryDto.d.ts +2 -12
  440. package/dist/generated/api/models/StencilVersionSummaryDto.d.ts.map +1 -1
  441. package/dist/generated/api/models/StencilVersionSummaryDto.js +10 -10
  442. package/dist/generated/api/models/StencilVersionSummaryDto.js.map +1 -1
  443. package/dist/generated/api/models/TemplateDataValidationError.d.ts +2 -8
  444. package/dist/generated/api/models/TemplateDataValidationError.d.ts.map +1 -1
  445. package/dist/generated/api/models/TemplateDataValidationError.js +2 -2
  446. package/dist/generated/api/models/TemplateDataValidationError.js.map +1 -1
  447. package/dist/generated/api/models/TemplateDataValidationProblemDetail.d.ts +66 -0
  448. package/dist/generated/api/models/TemplateDataValidationProblemDetail.d.ts.map +1 -0
  449. package/dist/generated/api/models/TemplateDataValidationProblemDetail.js +66 -0
  450. package/dist/generated/api/models/TemplateDataValidationProblemDetail.js.map +1 -0
  451. package/dist/generated/api/models/TemplateDataValidationResult.d.ts +16 -6
  452. package/dist/generated/api/models/TemplateDataValidationResult.d.ts.map +1 -1
  453. package/dist/generated/api/models/TemplateDataValidationResult.js +8 -2
  454. package/dist/generated/api/models/TemplateDataValidationResult.js.map +1 -1
  455. package/dist/generated/api/models/TemplateDocument.d.ts +2 -16
  456. package/dist/generated/api/models/TemplateDocument.d.ts.map +1 -1
  457. package/dist/generated/api/models/TemplateDocument.js +5 -3
  458. package/dist/generated/api/models/TemplateDocument.js.map +1 -1
  459. package/dist/generated/api/models/TemplateDto.d.ts +9 -23
  460. package/dist/generated/api/models/TemplateDto.d.ts.map +1 -1
  461. package/dist/generated/api/models/TemplateDto.js +8 -10
  462. package/dist/generated/api/models/TemplateDto.js.map +1 -1
  463. package/dist/generated/api/models/TemplateListResponse.d.ts +2 -6
  464. package/dist/generated/api/models/TemplateListResponse.d.ts.map +1 -1
  465. package/dist/generated/api/models/TemplateListResponse.js +2 -2
  466. package/dist/generated/api/models/TemplateListResponse.js.map +1 -1
  467. package/dist/generated/api/models/TemplateSummaryDto.d.ts +9 -15
  468. package/dist/generated/api/models/TemplateSummaryDto.d.ts.map +1 -1
  469. package/dist/generated/api/models/TemplateSummaryDto.js +8 -10
  470. package/dist/generated/api/models/TemplateSummaryDto.js.map +1 -1
  471. package/dist/generated/api/models/TenantDto.d.ts +9 -11
  472. package/dist/generated/api/models/TenantDto.d.ts.map +1 -1
  473. package/dist/generated/api/models/TenantDto.js +6 -8
  474. package/dist/generated/api/models/TenantDto.js.map +1 -1
  475. package/dist/generated/api/models/TenantListResponse.d.ts +2 -6
  476. package/dist/generated/api/models/TenantListResponse.d.ts.map +1 -1
  477. package/dist/generated/api/models/TenantListResponse.js +2 -2
  478. package/dist/generated/api/models/TenantListResponse.js.map +1 -1
  479. package/dist/generated/api/models/ThemeDto.d.ts +9 -25
  480. package/dist/generated/api/models/ThemeDto.d.ts.map +1 -1
  481. package/dist/generated/api/models/ThemeDto.js +8 -10
  482. package/dist/generated/api/models/ThemeDto.js.map +1 -1
  483. package/dist/generated/api/models/ThemeListResponse.d.ts +2 -6
  484. package/dist/generated/api/models/ThemeListResponse.d.ts.map +1 -1
  485. package/dist/generated/api/models/ThemeListResponse.js +2 -2
  486. package/dist/generated/api/models/ThemeListResponse.js.map +1 -1
  487. package/dist/generated/api/models/ThemeRef.d.ts +2 -8
  488. package/dist/generated/api/models/ThemeRef.d.ts.map +1 -1
  489. package/dist/generated/api/models/ThemeRef.js +3 -3
  490. package/dist/generated/api/models/ThemeRef.js.map +1 -1
  491. package/dist/generated/api/models/UpdateAttributeRequest.d.ts +3 -11
  492. package/dist/generated/api/models/UpdateAttributeRequest.d.ts.map +1 -1
  493. package/dist/generated/api/models/UpdateAttributeRequest.js +4 -4
  494. package/dist/generated/api/models/UpdateAttributeRequest.js.map +1 -1
  495. package/dist/generated/api/models/UpdateAttributeRequestCodeListBinding.d.ts +2 -6
  496. package/dist/generated/api/models/UpdateAttributeRequestCodeListBinding.d.ts.map +1 -1
  497. package/dist/generated/api/models/UpdateAttributeRequestCodeListBinding.js +2 -2
  498. package/dist/generated/api/models/UpdateAttributeRequestCodeListBinding.js.map +1 -1
  499. package/dist/generated/api/models/UpdateCodeListEntryHiddenRequest.d.ts +2 -4
  500. package/dist/generated/api/models/UpdateCodeListEntryHiddenRequest.d.ts.map +1 -1
  501. package/dist/generated/api/models/UpdateCodeListEntryHiddenRequest.js +2 -2
  502. package/dist/generated/api/models/UpdateCodeListEntryHiddenRequest.js.map +1 -1
  503. package/dist/generated/api/models/UpdateCodeListRequest.d.ts +2 -14
  504. package/dist/generated/api/models/UpdateCodeListRequest.d.ts.map +1 -1
  505. package/dist/generated/api/models/UpdateCodeListRequest.js +6 -6
  506. package/dist/generated/api/models/UpdateCodeListRequest.js.map +1 -1
  507. package/dist/generated/api/models/UpdateConsumerRequest.d.ts +2 -14
  508. package/dist/generated/api/models/UpdateConsumerRequest.d.ts.map +1 -1
  509. package/dist/generated/api/models/UpdateConsumerRequest.js +8 -8
  510. package/dist/generated/api/models/UpdateConsumerRequest.js.map +1 -1
  511. package/dist/generated/api/models/UpdateContractDraftRequest.d.ts +2 -8
  512. package/dist/generated/api/models/UpdateContractDraftRequest.d.ts.map +1 -1
  513. package/dist/generated/api/models/UpdateContractDraftRequest.js +3 -3
  514. package/dist/generated/api/models/UpdateContractDraftRequest.js.map +1 -1
  515. package/dist/generated/api/models/UpdateContractDraftResponse.d.ts +2 -10
  516. package/dist/generated/api/models/UpdateContractDraftResponse.d.ts.map +1 -1
  517. package/dist/generated/api/models/UpdateContractDraftResponse.js +5 -3
  518. package/dist/generated/api/models/UpdateContractDraftResponse.js.map +1 -1
  519. package/dist/generated/api/models/UpdateDraftRequest.d.ts +2 -4
  520. package/dist/generated/api/models/UpdateDraftRequest.d.ts.map +1 -1
  521. package/dist/generated/api/models/UpdateDraftRequest.js +2 -2
  522. package/dist/generated/api/models/UpdateDraftRequest.js.map +1 -1
  523. package/dist/generated/api/models/UpdateEnvironmentRequest.d.ts +2 -4
  524. package/dist/generated/api/models/UpdateEnvironmentRequest.d.ts.map +1 -1
  525. package/dist/generated/api/models/UpdateEnvironmentRequest.js +2 -2
  526. package/dist/generated/api/models/UpdateEnvironmentRequest.js.map +1 -1
  527. package/dist/generated/api/models/UpdateStencilDraftRequest.d.ts +2 -6
  528. package/dist/generated/api/models/UpdateStencilDraftRequest.d.ts.map +1 -1
  529. package/dist/generated/api/models/UpdateStencilDraftRequest.js +3 -3
  530. package/dist/generated/api/models/UpdateStencilDraftRequest.js.map +1 -1
  531. package/dist/generated/api/models/UpdateStencilRequest.d.ts +2 -8
  532. package/dist/generated/api/models/UpdateStencilRequest.d.ts.map +1 -1
  533. package/dist/generated/api/models/UpdateStencilRequest.js +3 -3
  534. package/dist/generated/api/models/UpdateStencilRequest.js.map +1 -1
  535. package/dist/generated/api/models/UpdateTemplateRequest.d.ts +2 -12
  536. package/dist/generated/api/models/UpdateTemplateRequest.d.ts.map +1 -1
  537. package/dist/generated/api/models/UpdateTemplateRequest.js +2 -2
  538. package/dist/generated/api/models/UpdateTemplateRequest.js.map +1 -1
  539. package/dist/generated/api/models/UpdateTenantRequest.d.ts +2 -4
  540. package/dist/generated/api/models/UpdateTenantRequest.d.ts.map +1 -1
  541. package/dist/generated/api/models/UpdateTenantRequest.js +2 -2
  542. package/dist/generated/api/models/UpdateTenantRequest.js.map +1 -1
  543. package/dist/generated/api/models/UpdateThemeRequest.d.ts +3 -15
  544. package/dist/generated/api/models/UpdateThemeRequest.d.ts.map +1 -1
  545. package/dist/generated/api/models/UpdateThemeRequest.js +5 -5
  546. package/dist/generated/api/models/UpdateThemeRequest.js.map +1 -1
  547. package/dist/generated/api/models/UpdateVariantRequest.d.ts +2 -8
  548. package/dist/generated/api/models/UpdateVariantRequest.d.ts.map +1 -1
  549. package/dist/generated/api/models/UpdateVariantRequest.js +3 -3
  550. package/dist/generated/api/models/UpdateVariantRequest.js.map +1 -1
  551. package/dist/generated/api/models/UpgradeCatalogRequest.d.ts +3 -4
  552. package/dist/generated/api/models/UpgradeCatalogRequest.d.ts.map +1 -1
  553. package/dist/generated/api/models/UpgradeCatalogRequest.js +2 -2
  554. package/dist/generated/api/models/UpgradeCatalogRequest.js.map +1 -1
  555. package/dist/generated/api/models/UpgradeCatalogResponse.d.ts +2 -12
  556. package/dist/generated/api/models/UpgradeCatalogResponse.d.ts.map +1 -1
  557. package/dist/generated/api/models/UpgradeCatalogResponse.js +3 -3
  558. package/dist/generated/api/models/UpgradeCatalogResponse.js.map +1 -1
  559. package/dist/generated/api/models/UpgradePreviewDto.d.ts +2 -16
  560. package/dist/generated/api/models/UpgradePreviewDto.d.ts.map +1 -1
  561. package/dist/generated/api/models/UpgradePreviewDto.js +2 -2
  562. package/dist/generated/api/models/UpgradePreviewDto.js.map +1 -1
  563. package/dist/generated/api/models/UpgradePreviewListResponse.d.ts +2 -4
  564. package/dist/generated/api/models/UpgradePreviewListResponse.d.ts.map +1 -1
  565. package/dist/generated/api/models/UpgradePreviewListResponse.js +2 -2
  566. package/dist/generated/api/models/UpgradePreviewListResponse.js.map +1 -1
  567. package/dist/generated/api/models/ValidateTemplateDataRequest.d.ts +21 -5
  568. package/dist/generated/api/models/ValidateTemplateDataRequest.d.ts.map +1 -1
  569. package/dist/generated/api/models/ValidateTemplateDataRequest.js +8 -2
  570. package/dist/generated/api/models/ValidateTemplateDataRequest.js.map +1 -1
  571. package/dist/generated/api/models/ValidationError.d.ts +3 -9
  572. package/dist/generated/api/models/ValidationError.d.ts.map +1 -1
  573. package/dist/generated/api/models/ValidationError.js +3 -3
  574. package/dist/generated/api/models/ValidationError.js.map +1 -1
  575. package/dist/generated/api/models/ValidationProblemDetail.d.ts +2 -14
  576. package/dist/generated/api/models/ValidationProblemDetail.d.ts.map +1 -1
  577. package/dist/generated/api/models/ValidationProblemDetail.js +2 -2
  578. package/dist/generated/api/models/ValidationProblemDetail.js.map +1 -1
  579. package/dist/generated/api/models/VariantDto.d.ts +9 -25
  580. package/dist/generated/api/models/VariantDto.d.ts.map +1 -1
  581. package/dist/generated/api/models/VariantDto.js +9 -11
  582. package/dist/generated/api/models/VariantDto.js.map +1 -1
  583. package/dist/generated/api/models/VariantListResponse.d.ts +2 -6
  584. package/dist/generated/api/models/VariantListResponse.d.ts.map +1 -1
  585. package/dist/generated/api/models/VariantListResponse.js +2 -2
  586. package/dist/generated/api/models/VariantListResponse.js.map +1 -1
  587. package/dist/generated/api/models/VariantSelectionAttribute.d.ts +2 -10
  588. package/dist/generated/api/models/VariantSelectionAttribute.d.ts.map +1 -1
  589. package/dist/generated/api/models/VariantSelectionAttribute.js +3 -3
  590. package/dist/generated/api/models/VariantSelectionAttribute.js.map +1 -1
  591. package/dist/generated/api/models/VariantSummaryDto.d.ts +9 -17
  592. package/dist/generated/api/models/VariantSummaryDto.d.ts.map +1 -1
  593. package/dist/generated/api/models/VariantSummaryDto.js +3 -5
  594. package/dist/generated/api/models/VariantSummaryDto.js.map +1 -1
  595. package/dist/generated/api/models/VersionDto.d.ts +2 -16
  596. package/dist/generated/api/models/VersionDto.d.ts.map +1 -1
  597. package/dist/generated/api/models/VersionDto.js +10 -10
  598. package/dist/generated/api/models/VersionDto.js.map +1 -1
  599. package/dist/generated/api/models/VersionListResponse.d.ts +2 -6
  600. package/dist/generated/api/models/VersionListResponse.d.ts.map +1 -1
  601. package/dist/generated/api/models/VersionListResponse.js +2 -2
  602. package/dist/generated/api/models/VersionListResponse.js.map +1 -1
  603. package/dist/generated/api/models/VersionSummaryDto.d.ts +2 -14
  604. package/dist/generated/api/models/VersionSummaryDto.d.ts.map +1 -1
  605. package/dist/generated/api/models/VersionSummaryDto.js +10 -10
  606. package/dist/generated/api/models/VersionSummaryDto.js.map +1 -1
  607. package/dist/generated/api/models/index.d.ts +3 -0
  608. package/dist/generated/api/models/index.d.ts.map +1 -1
  609. package/dist/generated/api/models/index.js +3 -0
  610. package/dist/generated/api/models/index.js.map +1 -1
  611. package/dist/generated/api/runtime.d.ts +14 -2
  612. package/dist/generated/api/runtime.d.ts.map +1 -1
  613. package/dist/generated/api/runtime.js +70 -5
  614. package/dist/generated/api/runtime.js.map +1 -1
  615. package/dist/generated/contractVersion.d.ts +1 -1
  616. package/dist/generated/contractVersion.js +1 -1
  617. package/dist/generated/knownProblemSlugs.d.ts +6 -0
  618. package/dist/generated/knownProblemSlugs.d.ts.map +1 -1
  619. package/dist/generated/knownProblemSlugs.js +6 -0
  620. package/dist/generated/knownProblemSlugs.js.map +1 -1
  621. package/dist/generated/modelValidation.d.ts +4 -2
  622. package/dist/generated/modelValidation.d.ts.map +1 -1
  623. package/dist/generated/modelValidation.js +20 -10
  624. package/dist/generated/modelValidation.js.map +1 -1
  625. package/package.json +3 -3
@@ -2,9 +2,9 @@
2
2
  /* eslint-disable */
3
3
  /**
4
4
  * Epistola API
5
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
5
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
6
6
  *
7
- * The version of the OpenAPI document: 1.3.0
7
+ * The version of the OpenAPI document: 1.4.0
8
8
  *
9
9
  *
10
10
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -1 +1 @@
1
- {"version":3,"file":"RemovedCatalogResourceDto.js","sourceRoot":"","sources":["../../../../src/generated/api/models/RemovedCatalogResourceDto.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAqB1C;;GAEG;AACH,MAAM,UAAU,mCAAmC,CAAC,KAAa;IAC7D,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,iCAAiC,CAAC,IAAS;IACvD,OAAO,sCAAsC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC/D,CAAC;AAED,MAAM,UAAU,sCAAsC,CAAC,IAAS,EAAE,mBAA4B;IAC1F,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;KACvB,CAAC;AACN,CAAC;AAED,MAAM,UAAU,+BAA+B,CAAC,IAAS;IACrD,OAAO,oCAAoC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC7D,CAAC;AAED,MAAM,UAAU,oCAAoC,CAAC,KAAwC,EAAE,mBAAmB,GAAY,KAAK;IAC/H,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;KACxB,CAAC;AACN,CAAC"}
1
+ {"version":3,"file":"RemovedCatalogResourceDto.js","sourceRoot":"","sources":["../../../../src/generated/api/models/RemovedCatalogResourceDto.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAiB1C;;GAEG;AACH,MAAM,UAAU,mCAAmC,CAAC,KAAa;IAC7D,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,iCAAiC,CAAC,IAAS;IACvD,OAAO,sCAAsC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC/D,CAAC;AAED,MAAM,UAAU,sCAAsC,CAAC,IAAS,EAAE,mBAA4B;IAC1F,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;KACvB,CAAC;AACN,CAAC;AAED,MAAM,UAAU,+BAA+B,CAAC,IAAS;IACrD,OAAO,oCAAoC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC7D,CAAC;AAED,MAAM,UAAU,oCAAoC,CAAC,KAAwC,EAAE,mBAAmB,GAAY,KAAK;IAC/H,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;KACxB,CAAC;AACN,CAAC"}
@@ -1,8 +1,8 @@
1
1
  /**
2
2
  * Epistola API
3
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
3
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
4
4
  *
5
- * The version of the OpenAPI document: 1.3.0
5
+ * The version of the OpenAPI document: 1.4.0
6
6
  *
7
7
  *
8
8
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -19,8 +19,6 @@
19
19
  export interface RotatePublicKeyRequest {
20
20
  /**
21
21
  * New PEM-encoded public key (RSA 2048+ or Ed25519)
22
- * @type {string}
23
- * @memberof RotatePublicKeyRequest
24
22
  */
25
23
  publicKey: string;
26
24
  }
@@ -1 +1 @@
1
- {"version":3,"file":"RotatePublicKeyRequest.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/RotatePublicKeyRequest.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;;;GAMG;AACH,MAAM,WAAW,sBAAsB;IACnC;;;;OAIG;IACH,SAAS,EAAE,MAAM,CAAC;CACrB;AAED;;GAEG;AACH,wBAAgB,gCAAgC,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,sBAAsB,CAG/F;AAED,wBAAgB,8BAA8B,CAAC,IAAI,EAAE,GAAG,GAAG,sBAAsB,CAEhF;AAED,wBAAgB,mCAAmC,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,sBAAsB,CAQnH;AAED,wBAAgB,4BAA4B,CAAC,IAAI,EAAE,GAAG,GAAG,sBAAsB,CAE9E;AAED,wBAAgB,iCAAiC,CAAC,KAAK,CAAC,EAAE,sBAAsB,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CASlI"}
1
+ {"version":3,"file":"RotatePublicKeyRequest.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/RotatePublicKeyRequest.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;;;GAMG;AACH,MAAM,WAAW,sBAAsB;IACnC;;OAEG;IACH,SAAS,EAAE,MAAM,CAAC;CACrB;AAED;;GAEG;AACH,wBAAgB,gCAAgC,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,sBAAsB,CAG/F;AAED,wBAAgB,8BAA8B,CAAC,IAAI,EAAE,GAAG,GAAG,sBAAsB,CAEhF;AAED,wBAAgB,mCAAmC,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,sBAAsB,CAQnH;AAED,wBAAgB,4BAA4B,CAAC,IAAI,EAAE,GAAG,GAAG,sBAAsB,CAE9E;AAED,wBAAgB,iCAAiC,CAAC,KAAK,CAAC,EAAE,sBAAsB,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CASlI"}
@@ -2,9 +2,9 @@
2
2
  /* eslint-disable */
3
3
  /**
4
4
  * Epistola API
5
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
5
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
6
6
  *
7
- * The version of the OpenAPI document: 1.3.0
7
+ * The version of the OpenAPI document: 1.4.0
8
8
  *
9
9
  *
10
10
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -1 +1 @@
1
- {"version":3,"file":"RotatePublicKeyRequest.js","sourceRoot":"","sources":["../../../../src/generated/api/models/RotatePublicKeyRequest.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAiB1C;;GAEG;AACH,MAAM,UAAU,gCAAgC,CAAC,KAAa;IAC1D,IAAI,CAAC,CAAC,WAAW,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,WAAW,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC9E,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,8BAA8B,CAAC,IAAS;IACpD,OAAO,mCAAmC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC5D,CAAC;AAED,MAAM,UAAU,mCAAmC,CAAC,IAAS,EAAE,mBAA4B;IACvF,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,WAAW,EAAE,IAAI,CAAC,WAAW,CAAC;KACjC,CAAC;AACN,CAAC;AAED,MAAM,UAAU,4BAA4B,CAAC,IAAS;IAClD,OAAO,iCAAiC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC1D,CAAC;AAED,MAAM,UAAU,iCAAiC,CAAC,KAAqC,EAAE,mBAAmB,GAAY,KAAK;IACzH,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,WAAW,EAAE,KAAK,CAAC,WAAW,CAAC;KAClC,CAAC;AACN,CAAC"}
1
+ {"version":3,"file":"RotatePublicKeyRequest.js","sourceRoot":"","sources":["../../../../src/generated/api/models/RotatePublicKeyRequest.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAe1C;;GAEG;AACH,MAAM,UAAU,gCAAgC,CAAC,KAAa;IAC1D,IAAI,CAAC,CAAC,WAAW,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,WAAW,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC9E,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,8BAA8B,CAAC,IAAS;IACpD,OAAO,mCAAmC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC5D,CAAC;AAED,MAAM,UAAU,mCAAmC,CAAC,IAAS,EAAE,mBAA4B;IACvF,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,WAAW,EAAE,IAAI,CAAC,WAAW,CAAC;KACjC,CAAC;AACN,CAAC;AAED,MAAM,UAAU,4BAA4B,CAAC,IAAS;IAClD,OAAO,iCAAiC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC1D,CAAC;AAED,MAAM,UAAU,iCAAiC,CAAC,KAAqC,EAAE,mBAAmB,GAAY,KAAK;IACzH,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,WAAW,EAAE,KAAK,CAAC,WAAW,CAAC;KAClC,CAAC;AACN,CAAC"}
@@ -1,8 +1,8 @@
1
1
  /**
2
2
  * Epistola API
3
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
3
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
4
4
  *
5
- * The version of the OpenAPI document: 1.3.0
5
+ * The version of the OpenAPI document: 1.4.0
6
6
  *
7
7
  *
8
8
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -17,26 +17,18 @@
17
17
  export interface Slot {
18
18
  /**
19
19
  * Unique identifier for a slot within a document.
20
- * @type {string}
21
- * @memberof Slot
22
20
  */
23
21
  id: string;
24
22
  /**
25
23
  * Parent node that owns this slot.
26
- * @type {string}
27
- * @memberof Slot
28
24
  */
29
25
  nodeId: string;
30
26
  /**
31
27
  * Semantic slot name (e.g. 'children', 'column-0', 'cell-0-1', 'body').
32
- * @type {string}
33
- * @memberof Slot
34
28
  */
35
29
  name: string;
36
30
  /**
37
31
  * Ordered child node IDs in this slot.
38
- * @type {Array<string>}
39
- * @memberof Slot
40
32
  */
41
33
  children: Array<string>;
42
34
  }
@@ -1 +1 @@
1
- {"version":3,"file":"Slot.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/Slot.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;GAIG;AACH,MAAM,WAAW,IAAI;IACjB;;;;OAIG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;;;OAIG;IACH,MAAM,EAAE,MAAM,CAAC;IACf;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;OAIG;IACH,QAAQ,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;CAC3B;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,IAAI,CAM3D;AAED,wBAAgB,YAAY,CAAC,IAAI,EAAE,GAAG,GAAG,IAAI,CAE5C;AAED,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,IAAI,CAW/E;AAED,wBAAgB,UAAU,CAAC,IAAI,EAAE,GAAG,GAAG,IAAI,CAE1C;AAED,wBAAgB,eAAe,CAAC,KAAK,CAAC,EAAE,IAAI,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAY9F"}
1
+ {"version":3,"file":"Slot.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/Slot.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;GAIG;AACH,MAAM,WAAW,IAAI;IACjB;;OAEG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;OAEG;IACH,MAAM,EAAE,MAAM,CAAC;IACf;;OAEG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;OAEG;IACH,QAAQ,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;CAC3B;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,IAAI,CAM3D;AAED,wBAAgB,YAAY,CAAC,IAAI,EAAE,GAAG,GAAG,IAAI,CAE5C;AAED,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,IAAI,CAW/E;AAED,wBAAgB,UAAU,CAAC,IAAI,EAAE,GAAG,GAAG,IAAI,CAE1C;AAED,wBAAgB,eAAe,CAAC,KAAK,CAAC,EAAE,IAAI,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAY9F"}
@@ -2,9 +2,9 @@
2
2
  /* eslint-disable */
3
3
  /**
4
4
  * Epistola API
5
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
5
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
6
6
  *
7
- * The version of the OpenAPI document: 1.3.0
7
+ * The version of the OpenAPI document: 1.4.0
8
8
  *
9
9
  *
10
10
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -1 +1 @@
1
- {"version":3,"file":"Slot.js","sourceRoot":"","sources":["../../../../src/generated/api/models/Slot.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAiC1C;;GAEG;AACH,MAAM,UAAU,cAAc,CAAC,KAAa;IACxC,IAAI,CAAC,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAChE,IAAI,CAAC,CAAC,QAAQ,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,QAAQ,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACxE,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC5E,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,YAAY,CAAC,IAAS;IAClC,OAAO,iBAAiB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC1C,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,IAAS,EAAE,mBAA4B;IACrE,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,IAAI,EAAE,IAAI,CAAC,IAAI,CAAC;QAChB,QAAQ,EAAE,IAAI,CAAC,QAAQ,CAAC;QACxB,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,UAAU,EAAE,IAAI,CAAC,UAAU,CAAC;KAC/B,CAAC;AACN,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAS;IAChC,OAAO,eAAe,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AACxC,CAAC;AAED,MAAM,UAAU,eAAe,CAAC,KAAmB,EAAE,mBAAmB,GAAY,KAAK;IACrF,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC;QACjB,QAAQ,EAAE,KAAK,CAAC,QAAQ,CAAC;QACzB,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,UAAU,EAAE,KAAK,CAAC,UAAU,CAAC;KAChC,CAAC;AACN,CAAC"}
1
+ {"version":3,"file":"Slot.js","sourceRoot":"","sources":["../../../../src/generated/api/models/Slot.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAyB1C;;GAEG;AACH,MAAM,UAAU,cAAc,CAAC,KAAa;IACxC,IAAI,CAAC,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAChE,IAAI,CAAC,CAAC,QAAQ,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,QAAQ,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACxE,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC5E,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,YAAY,CAAC,IAAS;IAClC,OAAO,iBAAiB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC1C,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,IAAS,EAAE,mBAA4B;IACrE,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,IAAI,EAAE,IAAI,CAAC,IAAI,CAAC;QAChB,QAAQ,EAAE,IAAI,CAAC,QAAQ,CAAC;QACxB,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,UAAU,EAAE,IAAI,CAAC,UAAU,CAAC;KAC/B,CAAC;AACN,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAS;IAChC,OAAO,eAAe,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AACxC,CAAC;AAED,MAAM,UAAU,eAAe,CAAC,KAAmB,EAAE,mBAAmB,GAAY,KAAK;IACrF,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC;QACjB,QAAQ,EAAE,KAAK,CAAC,QAAQ,CAAC;QACzB,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,UAAU,EAAE,KAAK,CAAC,UAAU,CAAC;KAChC,CAAC;AACN,CAAC"}
@@ -1,8 +1,8 @@
1
1
  /**
2
2
  * Epistola API
3
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
3
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
4
4
  *
5
- * The version of the OpenAPI document: 1.3.0
5
+ * The version of the OpenAPI document: 1.4.0
6
6
  *
7
7
  *
8
8
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -21,59 +21,47 @@ import type { StencilVersionSummaryDto } from './StencilVersionSummaryDto.js';
21
21
  export interface StencilDto {
22
22
  /**
23
23
  * Slug identifier of the stencil (e.g., "corporate-header")
24
- * @type {string}
25
- * @memberof StencilDto
24
+ *
25
+ * Sent by every server on contract 1.3.0 or later. Not required, because a server on an
26
+ * older 1.x contract omits it and a client must still read its responses: when it is
27
+ * absent, read `id`, which carries the same value. Required from 2.0.0, which removes
28
+ * `id` (epistola-app/epistola-contract#84).
29
+ *
26
30
  */
27
- slug: string;
31
+ slug?: string;
28
32
  /**
29
33
  * **Deprecated — use `slug`.** The same value, under the name the portable catalog
30
34
  * format already uses. Removed in 2.0.0 (epistola-app/epistola-contract#84).
31
35
  *
32
- * @type {string}
33
- * @memberof StencilDto
34
36
  * @deprecated
35
37
  */
36
38
  id: string;
37
39
  /**
38
40
  * Slug identifier of the tenant this stencil belongs to
39
- * @type {string}
40
- * @memberof StencilDto
41
41
  */
42
42
  tenantId: string;
43
43
  /**
44
44
  * Display name of the stencil
45
- * @type {string}
46
- * @memberof StencilDto
47
45
  */
48
46
  name: string;
49
47
  /**
50
48
  * Optional description of what this stencil provides
51
- * @type {string}
52
- * @memberof StencilDto
53
49
  */
54
50
  description?: string | null;
55
51
  /**
56
52
  * Tags for categorization and search
57
- * @type {Array<string>}
58
- * @memberof StencilDto
59
53
  */
60
54
  tags?: Array<string>;
61
55
  /**
62
56
  * Summary of all versions for this stencil
63
- * @type {Array<StencilVersionSummaryDto>}
64
- * @memberof StencilDto
65
57
  */
66
58
  versions: Array<StencilVersionSummaryDto>;
67
59
  /**
68
60
  * Timestamp when the stencil was created
69
- * @type {Date}
70
- * @memberof StencilDto
71
61
  */
72
62
  createdAt: Date;
73
63
  /**
74
64
  * Timestamp when the stencil was last modified
75
- * @type {Date}
76
- * @memberof StencilDto
77
65
  */
78
66
  lastModified: Date;
79
67
  }
@@ -1 +1 @@
1
- {"version":3,"file":"StencilDto.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilDto.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,+BAA+B,CAAC;AAQ9E;;;;;;;GAOG;AACH,MAAM,WAAW,UAAU;IACvB;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;;;;OAOG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;;;OAIG;IACH,QAAQ,EAAE,MAAM,CAAC;IACjB;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B;;;;OAIG;IACH,IAAI,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACrB;;;;OAIG;IACH,QAAQ,EAAE,KAAK,CAAC,wBAAwB,CAAC,CAAC;IAC1C;;;;OAIG;IACH,SAAS,EAAE,IAAI,CAAC;IAChB;;;;OAIG;IACH,YAAY,EAAE,IAAI,CAAC;CACtB;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,UAAU,CASvE;AAED,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,GAAG,GAAG,UAAU,CAExD;AAED,wBAAgB,uBAAuB,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,UAAU,CAgB3F;AAED,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,GAAG,GAAG,UAAU,CAEtD;AAED,wBAAgB,qBAAqB,CAAC,KAAK,CAAC,EAAE,UAAU,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAiB1G"}
1
+ {"version":3,"file":"StencilDto.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilDto.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,+BAA+B,CAAC;AAQ9E;;;;;;;GAOG;AACH,MAAM,WAAW,UAAU;IACvB;;;;;;;;OAQG;IACH,IAAI,CAAC,EAAE,MAAM,CAAC;IACd;;;;;OAKG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;OAEG;IACH,QAAQ,EAAE,MAAM,CAAC;IACjB;;OAEG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;OAEG;IACH,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B;;OAEG;IACH,IAAI,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACrB;;OAEG;IACH,QAAQ,EAAE,KAAK,CAAC,wBAAwB,CAAC,CAAC;IAC1C;;OAEG;IACH,SAAS,EAAE,IAAI,CAAC;IAChB;;OAEG;IACH,YAAY,EAAE,IAAI,CAAC;CACtB;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,UAAU,CAQvE;AAED,wBAAgB,kBAAkB,CAAC,IAAI,EAAE,GAAG,GAAG,UAAU,CAExD;AAED,wBAAgB,uBAAuB,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,UAAU,CAgB3F;AAED,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,GAAG,GAAG,UAAU,CAEtD;AAED,wBAAgB,qBAAqB,CAAC,KAAK,CAAC,EAAE,UAAU,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAiB1G"}
@@ -2,23 +2,21 @@
2
2
  /* eslint-disable */
3
3
  /**
4
4
  * Epistola API
5
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
5
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
6
6
  *
7
- * The version of the OpenAPI document: 1.3.0
7
+ * The version of the OpenAPI document: 1.4.0
8
8
  *
9
9
  *
10
10
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
11
11
  * https://openapi-generator.tech
12
12
  * Do not edit the class manually.
13
13
  */
14
- import { mapValues } from '../runtime.js';
14
+ import { mapValues, parseDate, parseDateTime, serializeDate, serializeDateTime } from '../runtime.js';
15
15
  import { StencilVersionSummaryDtoFromJSON, StencilVersionSummaryDtoFromJSONTyped, StencilVersionSummaryDtoToJSON, StencilVersionSummaryDtoToJSONTyped, } from './StencilVersionSummaryDto.js';
16
16
  /**
17
17
  * Check if a given object implements the StencilDto interface.
18
18
  */
19
19
  export function instanceOfStencilDto(value) {
20
- if (!('slug' in value) || value['slug'] === undefined)
21
- return false;
22
20
  if (!('id' in value) || value['id'] === undefined)
23
21
  return false;
24
22
  if (!('tenantId' in value) || value['tenantId'] === undefined)
@@ -41,15 +39,15 @@ export function StencilDtoFromJSONTyped(json, ignoreDiscriminator) {
41
39
  return json;
42
40
  }
43
41
  return {
44
- 'slug': json['slug'],
42
+ 'slug': json['slug'] == null ? undefined : json['slug'],
45
43
  'id': json['id'],
46
44
  'tenantId': json['tenantId'],
47
45
  'name': json['name'],
48
- 'description': json['description'] == null ? undefined : json['description'],
46
+ 'description': json['description'] === undefined ? undefined : json['description'] === null ? null : json['description'],
49
47
  'tags': json['tags'] == null ? undefined : json['tags'],
50
48
  'versions': (json['versions'].map(StencilVersionSummaryDtoFromJSON)),
51
- 'createdAt': (new Date(json['createdAt'])),
52
- 'lastModified': (new Date(json['lastModified'])),
49
+ 'createdAt': (json['createdAt'] == null ? json['createdAt'] : parseDateTime(json['createdAt'])),
50
+ 'lastModified': (json['lastModified'] == null ? json['lastModified'] : parseDateTime(json['lastModified'])),
53
51
  };
54
52
  }
55
53
  export function StencilDtoToJSON(json) {
@@ -67,8 +65,8 @@ export function StencilDtoToJSONTyped(value, ignoreDiscriminator = false) {
67
65
  'description': value['description'],
68
66
  'tags': value['tags'],
69
67
  'versions': (value['versions'].map(StencilVersionSummaryDtoToJSON)),
70
- 'createdAt': value['createdAt'].toISOString(),
71
- 'lastModified': value['lastModified'].toISOString(),
68
+ 'createdAt': value['createdAt'] == null ? value['createdAt'] : serializeDateTime(value['createdAt']),
69
+ 'lastModified': value['lastModified'] == null ? value['lastModified'] : serializeDateTime(value['lastModified']),
72
70
  };
73
71
  }
74
72
  //# sourceMappingURL=StencilDto.js.map
@@ -1 +1 @@
1
- {"version":3,"file":"StencilDto.js","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilDto.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAE1C,OAAO,EACH,gCAAgC,EAChC,qCAAqC,EACrC,8BAA8B,EAC9B,mCAAmC,GACtC,MAAM,+BAA+B,CAAC;AAsEvC;;GAEG;AACH,MAAM,UAAU,oBAAoB,CAAC,KAAa;IAC9C,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAChE,IAAI,CAAC,CAAC,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC5E,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC5E,IAAI,CAAC,CAAC,WAAW,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,WAAW,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC9E,IAAI,CAAC,CAAC,cAAc,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,cAAc,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpF,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,kBAAkB,CAAC,IAAS;IACxC,OAAO,uBAAuB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAChD,CAAC;AAED,MAAM,UAAU,uBAAuB,CAAC,IAAS,EAAE,mBAA4B;IAC3E,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,IAAI,EAAE,IAAI,CAAC,IAAI,CAAC;QAChB,UAAU,EAAE,IAAI,CAAC,UAAU,CAAC;QAC5B,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,aAAa,EAAE,IAAI,CAAC,aAAa,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC;QAC5E,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC;QACvD,UAAU,EAAE,CAAE,IAAI,CAAC,UAAU,CAAgB,CAAC,GAAG,CAAC,gCAAgC,CAAC,CAAC;QACpF,WAAW,EAAE,CAAC,IAAI,IAAI,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC;QAC1C,cAAc,EAAE,CAAC,IAAI,IAAI,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC;KACnD,CAAC;AACN,CAAC;AAED,MAAM,UAAU,gBAAgB,CAAC,IAAS;IACtC,OAAO,qBAAqB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC9C,CAAC;AAED,MAAM,UAAU,qBAAqB,CAAC,KAAyB,EAAE,mBAAmB,GAAY,KAAK;IACjG,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC;QACjB,UAAU,EAAE,KAAK,CAAC,UAAU,CAAC;QAC7B,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,aAAa,EAAE,KAAK,CAAC,aAAa,CAAC;QACnC,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,UAAU,EAAE,CAAE,KAAK,CAAC,UAAU,CAAgB,CAAC,GAAG,CAAC,8BAA8B,CAAC,CAAC;QACnF,WAAW,EAAE,KAAK,CAAC,WAAW,CAAC,CAAC,WAAW,EAAE;QAC7C,cAAc,EAAE,KAAK,CAAC,cAAc,CAAC,CAAC,WAAW,EAAE;KACtD,CAAC;AACN,CAAC"}
1
+ {"version":3,"file":"StencilDto.js","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilDto.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,SAAS,EAAE,aAAa,EAAE,aAAa,EAAE,iBAAiB,EAAE,MAAM,eAAe,CAAC;AAEtG,OAAO,EACH,gCAAgC,EAChC,qCAAqC,EACrC,8BAA8B,EAC9B,mCAAmC,GACtC,MAAM,+BAA+B,CAAC;AA0DvC;;GAEG;AACH,MAAM,UAAU,oBAAoB,CAAC,KAAa;IAC9C,IAAI,CAAC,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAChE,IAAI,CAAC,CAAC,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC5E,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,IAAI,CAAC,CAAC,UAAU,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC5E,IAAI,CAAC,CAAC,WAAW,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,WAAW,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IAC9E,IAAI,CAAC,CAAC,cAAc,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,cAAc,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpF,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,kBAAkB,CAAC,IAAS;IACxC,OAAO,uBAAuB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAChD,CAAC;AAED,MAAM,UAAU,uBAAuB,CAAC,IAAS,EAAE,mBAA4B;IAC3E,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC;QACvD,IAAI,EAAE,IAAI,CAAC,IAAI,CAAC;QAChB,UAAU,EAAE,IAAI,CAAC,UAAU,CAAC;QAC5B,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC;QACpB,aAAa,EAAE,IAAI,CAAC,aAAa,CAAC,KAAK,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC,KAAK,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC;QACxH,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC;QACvD,UAAU,EAAE,CAAE,IAAI,CAAC,UAAU,CAAgB,CAAC,GAAG,CAAC,gCAAgC,CAAC,CAAC;QACpF,WAAW,EAAE,CAAC,IAAI,CAAC,WAAW,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC;QAC/F,cAAc,EAAE,CAAC,IAAI,CAAC,cAAc,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC;KAC9G,CAAC;AACN,CAAC;AAED,MAAM,UAAU,gBAAgB,CAAC,IAAS;IACtC,OAAO,qBAAqB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAC9C,CAAC;AAED,MAAM,UAAU,qBAAqB,CAAC,KAAyB,EAAE,mBAAmB,GAAY,KAAK;IACjG,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC;QACjB,UAAU,EAAE,KAAK,CAAC,UAAU,CAAC;QAC7B,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,aAAa,EAAE,KAAK,CAAC,aAAa,CAAC;QACnC,MAAM,EAAE,KAAK,CAAC,MAAM,CAAC;QACrB,UAAU,EAAE,CAAE,KAAK,CAAC,UAAU,CAAgB,CAAC,GAAG,CAAC,8BAA8B,CAAC,CAAC;QACnF,WAAW,EAAE,KAAK,CAAC,WAAW,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,KAAK,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,iBAAiB,CAAC,KAAK,CAAC,WAAW,CAAC,CAAC;QACpG,cAAc,EAAE,KAAK,CAAC,cAAc,CAAC,IAAI,IAAI,CAAC,CAAC,CAAC,KAAK,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,iBAAiB,CAAC,KAAK,CAAC,cAAc,CAAC,CAAC;KACnH,CAAC;AACN,CAAC"}
@@ -1,8 +1,8 @@
1
1
  /**
2
2
  * Epistola API
3
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
3
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
4
4
  *
5
- * The version of the OpenAPI document: 1.3.0
5
+ * The version of the OpenAPI document: 1.4.0
6
6
  *
7
7
  *
8
8
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -19,14 +19,10 @@ import type { StencilSummaryDto } from './StencilSummaryDto.js';
19
19
  export interface StencilListResponse {
20
20
  /**
21
21
  * List of stencil summaries
22
- * @type {Array<StencilSummaryDto>}
23
- * @memberof StencilListResponse
24
22
  */
25
23
  items: Array<StencilSummaryDto>;
26
24
  /**
27
25
  *
28
- * @type {PageMeta}
29
- * @memberof StencilListResponse
30
26
  */
31
27
  page: PageMeta;
32
28
  }
@@ -1 +1 @@
1
- {"version":3,"file":"StencilListResponse.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilListResponse.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,eAAe,CAAC;AAO9C,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAQhE;;;;GAIG;AACH,MAAM,WAAW,mBAAmB;IAChC;;;;OAIG;IACH,KAAK,EAAE,KAAK,CAAC,iBAAiB,CAAC,CAAC;IAChC;;;;OAIG;IACH,IAAI,EAAE,QAAQ,CAAC;CAClB;AAED;;GAEG;AACH,wBAAgB,6BAA6B,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,mBAAmB,CAIzF;AAED,wBAAgB,2BAA2B,CAAC,IAAI,EAAE,GAAG,GAAG,mBAAmB,CAE1E;AAED,wBAAgB,gCAAgC,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,mBAAmB,CAS7G;AAED,wBAAgB,yBAAyB,CAAC,IAAI,EAAE,GAAG,GAAG,mBAAmB,CAExE;AAED,wBAAgB,8BAA8B,CAAC,KAAK,CAAC,EAAE,mBAAmB,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAU5H"}
1
+ {"version":3,"file":"StencilListResponse.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilListResponse.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,eAAe,CAAC;AAO9C,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAQhE;;;;GAIG;AACH,MAAM,WAAW,mBAAmB;IAChC;;OAEG;IACH,KAAK,EAAE,KAAK,CAAC,iBAAiB,CAAC,CAAC;IAChC;;OAEG;IACH,IAAI,EAAE,QAAQ,CAAC;CAClB;AAED;;GAEG;AACH,wBAAgB,6BAA6B,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,mBAAmB,CAIzF;AAED,wBAAgB,2BAA2B,CAAC,IAAI,EAAE,GAAG,GAAG,mBAAmB,CAE1E;AAED,wBAAgB,gCAAgC,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,mBAAmB,CAS7G;AAED,wBAAgB,yBAAyB,CAAC,IAAI,EAAE,GAAG,GAAG,mBAAmB,CAExE;AAED,wBAAgB,8BAA8B,CAAC,KAAK,CAAC,EAAE,mBAAmB,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAU5H"}
@@ -2,9 +2,9 @@
2
2
  /* eslint-disable */
3
3
  /**
4
4
  * Epistola API
5
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
5
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
6
6
  *
7
- * The version of the OpenAPI document: 1.3.0
7
+ * The version of the OpenAPI document: 1.4.0
8
8
  *
9
9
  *
10
10
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -1 +1 @@
1
- {"version":3,"file":"StencilListResponse.js","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilListResponse.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAE1C,OAAO,EACH,gBAAgB,EAChB,qBAAqB,EACrB,cAAc,EACd,mBAAmB,GACtB,MAAM,eAAe,CAAC;AAEvB,OAAO,EACH,yBAAyB,EACzB,8BAA8B,EAC9B,uBAAuB,EACvB,4BAA4B,GAC/B,MAAM,wBAAwB,CAAC;AAsBhC;;GAEG;AACH,MAAM,UAAU,6BAA6B,CAAC,KAAa;IACvD,IAAI,CAAC,CAAC,OAAO,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,OAAO,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACtE,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,2BAA2B,CAAC,IAAS;IACjD,OAAO,gCAAgC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AACzD,CAAC;AAED,MAAM,UAAU,gCAAgC,CAAC,IAAS,EAAE,mBAA4B;IACpF,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,OAAO,EAAE,CAAE,IAAI,CAAC,OAAO,CAAgB,CAAC,GAAG,CAAC,yBAAyB,CAAC,CAAC;QACvE,MAAM,EAAE,gBAAgB,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;KACzC,CAAC;AACN,CAAC;AAED,MAAM,UAAU,yBAAyB,CAAC,IAAS;IAC/C,OAAO,8BAA8B,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AACvD,CAAC;AAED,MAAM,UAAU,8BAA8B,CAAC,KAAkC,EAAE,mBAAmB,GAAY,KAAK;IACnH,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,OAAO,EAAE,CAAE,KAAK,CAAC,OAAO,CAAgB,CAAC,GAAG,CAAC,uBAAuB,CAAC,CAAC;QACtE,MAAM,EAAE,cAAc,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC;KACxC,CAAC;AACN,CAAC"}
1
+ {"version":3,"file":"StencilListResponse.js","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilListResponse.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,oBAAoB;AACpB;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,eAAe,CAAC;AAE1C,OAAO,EACH,gBAAgB,EAChB,qBAAqB,EACrB,cAAc,EACd,mBAAmB,GACtB,MAAM,eAAe,CAAC;AAEvB,OAAO,EACH,yBAAyB,EACzB,8BAA8B,EAC9B,uBAAuB,EACvB,4BAA4B,GAC/B,MAAM,wBAAwB,CAAC;AAkBhC;;GAEG;AACH,MAAM,UAAU,6BAA6B,CAAC,KAAa;IACvD,IAAI,CAAC,CAAC,OAAO,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,OAAO,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACtE,IAAI,CAAC,CAAC,MAAM,IAAI,KAAK,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,SAAS;QAAE,OAAO,KAAK,CAAC;IACpE,OAAO,IAAI,CAAC;AAChB,CAAC;AAED,MAAM,UAAU,2BAA2B,CAAC,IAAS;IACjD,OAAO,gCAAgC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AACzD,CAAC;AAED,MAAM,UAAU,gCAAgC,CAAC,IAAS,EAAE,mBAA4B;IACpF,IAAI,IAAI,IAAI,IAAI,EAAE,CAAC;QACf,OAAO,IAAI,CAAC;IAChB,CAAC;IACD,OAAO;QAEH,OAAO,EAAE,CAAE,IAAI,CAAC,OAAO,CAAgB,CAAC,GAAG,CAAC,yBAAyB,CAAC,CAAC;QACvE,MAAM,EAAE,gBAAgB,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;KACzC,CAAC;AACN,CAAC;AAED,MAAM,UAAU,yBAAyB,CAAC,IAAS;IAC/C,OAAO,8BAA8B,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AACvD,CAAC;AAED,MAAM,UAAU,8BAA8B,CAAC,KAAkC,EAAE,mBAAmB,GAAY,KAAK;IACnH,IAAI,KAAK,IAAI,IAAI,EAAE,CAAC;QAChB,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,OAAO;QAEH,OAAO,EAAE,CAAE,KAAK,CAAC,OAAO,CAAgB,CAAC,GAAG,CAAC,uBAAuB,CAAC,CAAC;QACtE,MAAM,EAAE,cAAc,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC;KACxC,CAAC;AACN,CAAC"}
@@ -1,8 +1,8 @@
1
1
  /**
2
2
  * Epistola API
3
- * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **Bearer JWT**: `Authorization: Bearer <jwt>` using OAuth 2.0 Client Credentials or self-signed JWTs - **API key**: `Authorization: ApiKey <key>` for static tenant API keys The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. Permissions and allowed tenants are managed in Epistola\'s consumer record, not in JWT claims. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
3
+ * Document template management API for Epistola Suite. ## Versioning This API uses header-based versioning via the Accept header. Use `application/vnd.epistola.v1+json` for API version 1. ## Authentication The API accepts authentication through the `Authorization` header: - **API key**: `Authorization: ApiKey <key>` for static tenant API keys. This is the supported method. A tenant manager issues each key for one tenant with a set of tenant roles. - **Bearer JWT** (**experimental**): `Authorization: Bearer <jwt>`, either issued by an OAuth 2.0 identity provider or self-signed with a key pair registered through the Consumers API. Epistola Suite may not implement the consumer model these rely on yet, and the flow may still change. The legacy `X-API-Key` header remains supported for existing integrations, but is deprecated. New API-key integrations should use `Authorization: ApiKey <key>`. See the [Authentication Guide](/docs/auth.md) for details. ## Client Identity All requests must include the following headers for client identification: - **`User-Agent`** (required) — identifies the client software stack using standard [RFC 9110 §10.1.5](https://www.rfc-editor.org/rfc/rfc9110#name-user-agent) product tokens. The first token **must** be `epistola-contract/{version}` indicating the contract version the client was built against. Additional product/version pairs can be appended to describe the full software stack. Example: `epistola-contract/x.y.z valtimo-epistola-plugin/1.2.0 gzac/5.0.0` - **`X-EP-Node-Id`** (required) — identifies the specific client node. Use the Kubernetes pod name, container ID, or hostname. In local/dev environments, the machine hostname is acceptable. The generated Epistola client libraries set both headers automatically — `User-Agent` with the contract version, and `X-EP-Node-Id` with the hostname. Consumers wrapping the client library can append additional product tokens to `User-Agent` for their own software and override the node ID as needed. ## Error Responses The API uses [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) for error responses. Error responses have `Content-Type: application/problem+json` and include the following fields: - `type` (string, URI) — identifies the problem type; the stable, machine-readable discriminator clients should switch on - `title` (string) — short human-readable summary - `status` (integer) — HTTP status code - `detail` (string, optional) — human-readable explanation of this occurrence - `instance` (string, URI, optional) — identifies this specific occurrence Problem `type` URIs use the `https://epistola.app/errors/{slug}` namespace and resolve to human-readable HTML documentation for that problem type. A response may also carry domain-specific extension members as top-level fields; clients should ignore members they do not recognize. For validation errors (`type: .../validation-error`), the response also includes an `errors` array with field-level details. The canonical problem `type` slugs are registered in [`docs/error-types.md`](docs/error-types.md); the machine-readable registry is this document\'s top-level `x-problem-types` extension. ## Authorization Access is controlled via Suite permissions such as `TEMPLATE_VIEW`, `TEMPLATE_EDIT`, `DOCUMENT_GENERATE`, and `CATALOG_MANAGE`. Tenant permissions are derived from the Suite tenant roles (`CONTENT_VIEWER`, `CONTENT_AUTHOR`, `DOCUMENT_GENERATOR`, `CONTENT_PUBLISHER`, `TENANT_ADMINISTRATOR`) or from the roles stored on an API key. Platform-only tenant management uses the `TENANT_MANAGER` platform role.
4
4
  *
5
- * The version of the OpenAPI document: 1.3.0
5
+ * The version of the OpenAPI document: 1.4.0
6
6
  *
7
7
  *
8
8
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -17,59 +17,47 @@
17
17
  export interface StencilSummaryDto {
18
18
  /**
19
19
  * Slug identifier of the stencil
20
- * @type {string}
21
- * @memberof StencilSummaryDto
20
+ *
21
+ * Sent by every server on contract 1.3.0 or later. Not required, because a server on an
22
+ * older 1.x contract omits it and a client must still read its responses: when it is
23
+ * absent, read `id`, which carries the same value. Required from 2.0.0, which removes
24
+ * `id` (epistola-app/epistola-contract#84).
25
+ *
22
26
  */
23
- slug: string;
27
+ slug?: string;
24
28
  /**
25
29
  * **Deprecated — use `slug`.** The same value, under the name the portable catalog
26
30
  * format already uses. Removed in 2.0.0 (epistola-app/epistola-contract#84).
27
31
  *
28
- * @type {string}
29
- * @memberof StencilSummaryDto
30
32
  * @deprecated
31
33
  */
32
34
  id: string;
33
35
  /**
34
36
  * Slug identifier of the tenant this stencil belongs to
35
- * @type {string}
36
- * @memberof StencilSummaryDto
37
37
  */
38
38
  tenantId: string;
39
39
  /**
40
40
  * Display name of the stencil
41
- * @type {string}
42
- * @memberof StencilSummaryDto
43
41
  */
44
42
  name: string;
45
43
  /**
46
44
  * Optional description of what this stencil provides
47
- * @type {string}
48
- * @memberof StencilSummaryDto
49
45
  */
50
46
  description?: string | null;
51
47
  /**
52
48
  * Tags for categorization and search
53
- * @type {Array<string>}
54
- * @memberof StencilSummaryDto
55
49
  */
56
50
  tags?: Array<string>;
57
51
  /**
58
52
  * Version number of the latest published version, or null if no version is published
59
- * @type {number}
60
- * @memberof StencilSummaryDto
61
53
  */
62
54
  latestPublishedVersion: number | null;
63
55
  /**
64
56
  * Timestamp when the stencil was created
65
- * @type {Date}
66
- * @memberof StencilSummaryDto
67
57
  */
68
58
  createdAt: Date;
69
59
  /**
70
60
  * Timestamp when the stencil was last modified
71
- * @type {Date}
72
- * @memberof StencilSummaryDto
73
61
  */
74
62
  lastModified: Date;
75
63
  }
@@ -1 +1 @@
1
- {"version":3,"file":"StencilSummaryDto.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilSummaryDto.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAC9B;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;;;;OAOG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;;;OAIG;IACH,QAAQ,EAAE,MAAM,CAAC;IACjB;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;OAIG;IACH,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B;;;;OAIG;IACH,IAAI,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACrB;;;;OAIG;IACH,sBAAsB,EAAE,MAAM,GAAG,IAAI,CAAC;IACtC;;;;OAIG;IACH,SAAS,EAAE,IAAI,CAAC;IAChB;;;;OAIG;IACH,YAAY,EAAE,IAAI,CAAC;CACtB;AAED;;GAEG;AACH,wBAAgB,2BAA2B,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,iBAAiB,CASrF;AAED,wBAAgB,yBAAyB,CAAC,IAAI,EAAE,GAAG,GAAG,iBAAiB,CAEtE;AAED,wBAAgB,8BAA8B,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,iBAAiB,CAgBzG;AAED,wBAAgB,uBAAuB,CAAC,IAAI,EAAE,GAAG,GAAG,iBAAiB,CAEpE;AAED,wBAAgB,4BAA4B,CAAC,KAAK,CAAC,EAAE,iBAAiB,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAiBxH"}
1
+ {"version":3,"file":"StencilSummaryDto.d.ts","sourceRoot":"","sources":["../../../../src/generated/api/models/StencilSummaryDto.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;GAUG;AAGH;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAC9B;;;;;;;;OAQG;IACH,IAAI,CAAC,EAAE,MAAM,CAAC;IACd;;;;;OAKG;IACH,EAAE,EAAE,MAAM,CAAC;IACX;;OAEG;IACH,QAAQ,EAAE,MAAM,CAAC;IACjB;;OAEG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;OAEG;IACH,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B;;OAEG;IACH,IAAI,CAAC,EAAE,KAAK,CAAC,MAAM,CAAC,CAAC;IACrB;;OAEG;IACH,sBAAsB,EAAE,MAAM,GAAG,IAAI,CAAC;IACtC;;OAEG;IACH,SAAS,EAAE,IAAI,CAAC;IAChB;;OAEG;IACH,YAAY,EAAE,IAAI,CAAC;CACtB;AAED;;GAEG;AACH,wBAAgB,2BAA2B,CAAC,KAAK,EAAE,MAAM,GAAG,KAAK,IAAI,iBAAiB,CAQrF;AAED,wBAAgB,yBAAyB,CAAC,IAAI,EAAE,GAAG,GAAG,iBAAiB,CAEtE;AAED,wBAAgB,8BAA8B,CAAC,IAAI,EAAE,GAAG,EAAE,mBAAmB,EAAE,OAAO,GAAG,iBAAiB,CAgBzG;AAED,wBAAgB,uBAAuB,CAAC,IAAI,EAAE,GAAG,GAAG,iBAAiB,CAEpE;AAED,wBAAgB,4BAA4B,CAAC,KAAK,CAAC,EAAE,iBAAiB,GAAG,IAAI,EAAE,mBAAmB,GAAE,OAAe,GAAG,GAAG,CAiBxH"}