I am experiencing issues with the current implementation of apiCategories. In apiCategories.json, you can only specify the name of the API category. However, to use this category in an apiProduct inside the apiDocs document, you need to reference it by its ID using the categoryIds tag. As the Id however, is not included in the API category creation request, it is generated randomly, making it unusable.
Since the API category creation endpoint accepts four parameters: id, siteId, name, and updateTime, can you allow the ID to be specified in the creation request? This would ensure the categories are usable.
I am experiencing issues with the current implementation of apiCategories. In apiCategories.json, you can only specify the name of the API category. However, to use this category in an apiProduct inside the apiDocs document, you need to reference it by its ID using the categoryIds tag. As the Id however, is not included in the API category creation request, it is generated randomly, making it unusable.
Since the API category creation endpoint accepts four parameters: id, siteId, name, and updateTime, can you allow the ID to be specified in the creation request? This would ensure the categories are usable.