ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Fiber recycles its Context object for zero-allocation performance. Build versioned APIs with grouped middleware while copying request data before spawning goroutines to prevent data races.
Sanity's Content Lake is versioned by date strings rather than semantic majors: a client declares an apiVersion such as 2023-05-03 , and query and mutation behavior is gated on that pinned date. Separately, Sanity Studio v3 is a React application with its own Node.js and React runtime requirements, so a Studio major upgrade is a toolchain change rather than
tRPC Schema Versioning In tRPC v11, server-to-client type inference occurs at build time. When a router's input or output schema is modified and deployed, clients compiled against the newer inferred types expect a specific data structure. If the server is subsequently rolled back to a previous schema version, a runtime drift occurs between the deployed clien
A small application needs to move from ShotGrid REST API v5 to v6 without an outage. The migration plan relies on the documented ability to address different major versions in the same environment and on OAuth2 token refresh to keep authentication active while the client configuration changes. The integration boundary is between the ShotGrid REST API version
Version pinning required for LinkedIn Marketing APIs LinkedIn's versioned REST endpoints require a Linkedin-Version header in YYYYMM format. Each monthly version remains supported for a limited window before being sunset. When a request targets a sunset version, the platform responds with a 426-style version-not-supported failure instead of silently routing
Goal I need to publish a breaking schema change in an OpenAPI 3.0 or 3.1 document while keeping older clients able to roll back to the previous schema without client regeneration. Constraints OpenAPI describes one API version and provides no standard field for prior schema versions, rollback links, or sunset dates. The deprecated keyword flags an operation f
An application deploys a new gRPC service version that adds optional fields to existing protobuf messages. The older binary, still running in production, must continue to parse messages produced under the newer schema. If the service is rolled back to the previous binary, does the older version reliably interpret the additional fields without data loss or mi
Integration boundary We are building a sync service that reads and occasionally updates pages on a Confluence Cloud site. Both supported API families are available: v1 ( /rest/api/... ) and v2 ( /api/v2/... ). They are not drop-in interchangeable, and we must pick a strategy before writing the client layer. Where we are uncertain From the documentation, v1 l
Assume a REST API documented with OpenAPI 3.0.x, where consumers generate their own clients from the published document. A recent schema change added a new enum value to a response field and made one previously optional request field required. The deployment now needs to be rolled back, but some consumers may have already regenerated clients against the newe
fiber
go
sanity
typescript
shotgrid
linkedin
grpc
swagger