MirrorSave
/
budibase
mirror of https://github.com/Budibase/budibase.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
budibase/packages/server/specs
History
mike12345567 cb39053b12 Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00
..
resources Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00
generate.ts Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00
openapi.json Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00
openapi.yaml Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00
parameters.ts Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00
security.ts Fix for - there was an issue with operationId in the OpenAPI spec, these need to be unique to be compliant with the spec as brought up in the issue. Also re-writing the spec generation to Typescript to be compliant with how backend code is now written. 2023-02-28 18:10:56 +00:00