Highlights
- Pro
- Security Bug Bounty Hunter
- 3 discussions answered
Pinned
958 contributions in the last year
Less
More
Activity overview
Contributed to
graphql/graphql-js,
graphql/graphql-relay-js,
graphql/express-graphql
and 5 other
repositories
Contribution activity
October 2021
Created 19 commits in 2 repositories
Created a pull request in graphql/graphql-spec that received 3 comments
Add descriptions to executable definitions
Was already discussed during WG: https://github.com/graphql/graphql-wg/blob/main/notes/2021-04-01.md#adding-descriptions-to-queries-and-fragments-ivan
+17
−5
•
3
comments
Opened 16 other pull requests in 2 repositories
graphql/graphql-js
14
merged
- GraphQLError: use enumerable properties
-
expectJSON: return custom object instead of
expect -
Move deprecated
SubscriptionArgsto 'src/subscription' - execute: Correctly report missing root type error
-
Reuse
groupByin validation rules -
Added 'GraphQLSchema.getRootType' and deprecate
getOperationRootType -
README: remove credits for
*.d.tsfiles - Remove unnecessary Promise.resolve and Promise.reject
- integrationTests/ts: Simplify extensions tests
-
Move validation of names into
GraphQL*constructors - assertValidName: share character classes with lexer
- Improve documentation of validation rules
- VariablesAreInputTypesRule: add test for ignoring unknown types
- validation: restrict maximum number of errors to 100 by default
graphql/graphql-wg
2
merged
Reviewed 10 pull requests in 1 repository
graphql/graphql-js
10 pull requests
- fix: change OperationTypeNode to enum
- Properly name the root field execution functions
- execute: Correctly report missing root type error
- Add 'UniqueArgumentDefinitionNamesRule' validation rule
- Deprecate SubscriptionArgs and broaden ExecutionArgs
-
Added 'GraphQLSchema.getRootType' and deprecate
getOperationRootType - Deprecate SubscriptionArgs and broaden ExecutionArgs
- Align calls of buildExecutionContext
- Deprecate 'graphql/subscriptions' and move code to 'execution'
- refactor: consolidate subscription into execution
Created an issue in graphql/graphql-spec that received 2 comments
Add why field to GraphQL Errors
TL;DR:
This RFC proposes adding the why field to GraphQL errors that contain a list of reasons why this error happened.
Problem Statement
Sometimes…
2
comments

