[povilasjurcys]

What's the reason for this feature?

Currently, be_successful_graphql_request reports two false positives in controller specs:

• A DateTime! field returning a Date fails, though GraphQL serializes it correctly.
• A GraphqlRails model whose field reads graphql_context raises, because the matcher never sets it (e.g., in shift decorators).

This PR:

• checks ISO8601DateTime and ISO8601Date through coerce_result. The other built-in scalars keep their class lists, since their coerce_result accepts almost anything.
• passes the request's context (response.context) down to field calls. A field runs inside with_graphql_context when its type is one GraphqlRails built, matching GraphqlRails' resolver behavior. graphql-ruby calls stay on NullContext.

Reviewers should know:

• Date fields now accept anything Date.parse(to_s) accepts, such as 20240101, as GraphQL does. This is documented in the CHANGELOG.
• Still open: the test context only supports []/fetch/key?/to_h, so decorators that call graphql_context&.dig(...) will fail the matcher if the context doesn't support deep navigation. Other open items: the CHANGELOG needs the graphql_rails version once released, no spec pins the respond_to?(:with_graphql_context) guard yet, and the new graphql_context: keyword belongs under "Added".
• With an older graphql_rails version (no response.context), fields run without a context, as before.

Testing done: gem suite, 122 examples, 0 failures. Validated with updated gem branches in an application test suite where date fields pass the matcher and decorators resolve graphql_context correctly with the request context (and fail without it).

[Copilot]

🟡 Changes recommended

The limited request context introduces matcher failures for fields using graphql_context&.dig.

1 open issue

• Limited GraphQL context lacks dig, causing NoMethodError · New

What changed in this PR

Aligns date validation with GraphQL serialization and passes request context to GraphqlRails model fields.

Changes:

• Validates date scalars through coerce_result.
• Propagates optional context through field validation.
• Adds regression specs and changelog entries.

File	Description
spec/​lib/​rspec_extra_matchers/​graphql_matchers/​type_matcher_spec.rb	Covers date coercion and model context behavior.
spec/​lib/​rspec_extra_matchers/​graphql_matchers/​successful_graphql_controller_response_matcher_spec.rb	Tests request-context forwarding.
lib/​rspec_extra_matchers/​graphql_matchers/​type_matcher.rb	Accepts and forwards optional context.
lib/​rspec_extra_matchers/​graphql_matchers/​successful_graphql_controller_response_matcher.rb	Retrieves context from supported responses.
lib/​rspec_extra_matchers/​graphql_matchers/​assert_type_and_value.rb	Coerces date scalars and scopes model context.
CHANGELOG.md	Documents validation and context changes.

_{Review effort: Balanced}