Collection of custom GraphQL types like Email, URL, password and many more
GitHub GraphQL API client for browsers and Node
A collection of scalar types not included in base GraphQL.
Types for building GraphQL language services for IDEs
A spec-compliant client-side GraphQL implementation
TypeScript definitions for graphql-upload
Export GraphQL Armor types.
Tooling for GraphQL. Compare GraphQL Schemas, check documents, find breaking changes, find similar types.
GraphQL schema builder from different data sources with middleware extensions.
Custom GraphQL Types
GraphQL subscriptions for node.js
TypeScript types for Apollo Server info.cacheControl
The spec-compliant & magical GraphQL query language engine in the TypeScript type system
Tooling for GraphQL. Compare GraphQL Schemas, check documents, find breaking changes, find similar types.
GraphQL codegen plugin that generates only the types used in the operations
full service, official monaco mode for GraphQL
Send parameterized requests to GitHub's APIs with sensible defaults in browsers and Node
Preset for graphql-codegen to parse and type queries to Shopify APIs
GraphQL Codegen plugin for building mock data
GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration).
Fork of graphql-upload@8 that works with graphql@15 for compatibility with apollo-server@2
the complete solution for node.js command-line programs
Command line tool and package to validate GraphQL schemas against a set of rules.
JSON scalar types for GraphQL.js
rails-fields gem provides robust field type enforcement for ActiveRecord models in Ruby on Rails applications. It includes utility methods for type validation, logging, and field mappings between GraphQL and ActiveRecord types Custom error classes provide clear diagnostics for field-related issues, making it easier to maintain consistent data models.
The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.