UNPKG

@lokalise/api-contracts

Version:

Key idea behind API contracts: backend owns entire definition for the route, including its path, HTTP method used and response structure expectations, and exposes it as a part of its API schemas. Then frontend consumes that definition instead of forming f

4 lines 138 B
export * from "./apiContracts.js"; export * from "./HttpStatusCodes.js"; export * from "./pathUtils.js"; //# sourceMappingURL=index.js.map