graphql-ruby
https://github.com/rmosolgo/graphql-ruby
Ruby
Ruby implementation of GraphQL
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
3 Subscribers
Add a CodeTriage badge to graphql-ruby
Help out
- Issues
- Make Schema.from_definition about 45% faster on large schemas
- Don't end C lexer block strings with a single trailing quote
- rescue_from handler return values during argument coercion are passed to resolve as the argument's value
- Fix rescue_from return values leaking into resolve as argument values
- Coerce input values in a single pass
- Visibility::Migration: actually compare list members
- Inherit directives on interfaces from included interfaces; keep repeated repeatable directives
- Move Execution::FieldResolveStep to typed: true
- Move Schema::BuildFromDefinition to typed: true
- Resolve built-in lazy values in Execution::Next
- Docs
- GraphQL::Schema.logger_for
- GraphQL::Schema.complexity_cost_calculation_mode_for
- GraphQL::Schema.complexity_cost_calculation_mode
- GraphQL::Schema.legacy_complexity_cost_calculation_mismatch
- GraphQL::InvalidNullError#is_from_array
- GraphQL::Execution::Multiplex#logger
- GraphQL::Analysis::QueryComplexity#legacy_merged_max_complexity
- GraphQL::Analysis::QueryComplexity::ScopedTypeComplexity#composite?
- GraphQL::Schema.legacy_invalid_return_type_conflicts
- GraphQL::Schema.allow_legacy_invalid_return_type_conflicts