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/resources
History
mike12345567 7673673db2 Updating RelationshipTypes -> RelationshipType. 2023-07-21 12:57:47 +01:00
..
utils Fix for #9778 - 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
application.ts Updating metrics endpoint to have examples of expected data format - show OpenMetrics response. 2023-03-06 15:55:55 +00:00
index.ts Updating metrics endpoint to have examples of expected data format - show OpenMetrics response. 2023-03-06 15:55:55 +00:00
metrics.ts Updating metrics endpoint to have examples of expected data format - show OpenMetrics response. 2023-03-06 15:55:55 +00:00
misc.ts Fix for #9778 - 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
query.ts Fix for #9778 - 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
row.ts Fix for #9778 - 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
table.ts Updating RelationshipTypes -> RelationshipType. 2023-07-21 12:57:47 +01:00
user.ts Fix for #9778 - 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