Fullstack TypeScript toolkit that enhances Prisma ORM with flexible Authorization layer for RBAC/ABAC/PBAC/ReBAC, offering auto-generated type-safe APIs and frontend hooks.
For GET/DELETE operations, the query args is passed as JSON-stringified text in the query parameter q.
This conforms with the functionality of the plugin.
However, below that statement, an example is provided:
Check here for the generated specification for a blogging app.
This example appears to have used an older specification with a different syntax than what the current version of @zenstackhq/openapi. The generated specification does not mirror the GET syntax as described in the documentation.
In the linked example, the OpenAPI document has specified different parameters than what currently get generated, under the paths section for each get method:
The example is thus misleading as the actual code samples (as provided by Swagger UI) do not provide working syntax for the plugin's generated GET endpoints, at least with only basic configuration for the latest version (alpha.87).
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Description and expected behavior The documentation for
@zenstackhq/openapi
should include up-to-date examples that match the documentation.In the "Generated API paths" section of the documentation (https://zenstack.dev/docs/reference/plugins/openapi#generated-api-paths), the following syntax is mentioned:
This conforms with the functionality of the plugin.
However, below that statement, an example is provided:
This example appears to have used an older specification with a different syntax than what the current version of
@zenstackhq/openapi
. The generated specification does not mirror theGET
syntax as described in the documentation.In the linked example, the OpenAPI document has specified different parameters than what currently get generated, under the paths section for each get method:
What is currently generated by the plugin is:
The example is thus misleading as the actual code samples (as provided by Swagger UI) do not provide working syntax for the plugin's generated
GET
endpoints, at least with only basic configuration for the latest version (alpha.87).Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):