ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal The objective is to keep a Prisma schema that matches a PostgreSQL database containing mixed‑case column identifiers (e.g., "UserID") usable in both local development and a production environment. Locally the schema is generated by introspection, but Prisma converts all column names to lower case by default, which can cause runtime failures when the pro
Directive Introspection Behavior Across GraphQL Spec Versions Goal: Determine whether a GraphQL server should expose directive definitions through the introspection system and how this exposure should be handled for both built‑in and custom directives. Constraints: The GraphQL specification did not standardize directive introspection until the 2018‑06 releas
Goal: Identify the conditions under which the Vala compiler retains the nullable annotation ( ? ), when generating a VAPI file via valac --vapi for a method parameter. Constraint: The Vala documentation does not specify a deterministic rule, and observed output differs depending on whether GObject Introspection data is available during compilation, leading t
Goal Determine an appropriate cache lifetime for OAuth introspection responses that satisfies low-latency validation while providing acceptable revocation guarantees for latency-sensitive APIs. Constraints and uncertainty OAuth 2.0 (RFC 6749) and JWT profiles (RFC 7519) express time-based claims in UTC; the spec does not prescribe how an authorization server
In production GraphQL deployments, teams must choose between fully disabling introspection to prevent unauthenticated schema discovery and conditionally allowing it for authenticated developer tooling. A specific complication arises because some GraphQL server implementations and middleware treat the __schema and __type meta-fields independently, meaning a p
Goal and Context We need to verify that Apollo Server correctly reports @deprecated fields during introspection, especially across recent releases. The GraphQL specification mandates that a deprecated field must expose isDeprecated: true and a deprecationReason string via the __type introspection system. Historically, Apollo Server 2.x adhered to this contra
prisma
graphql
oauth