Skip to content

Stricter parseValue coercion for built-in scalars #3191

Closed

Description

@dondonz

This is an issue to track the progress of stricter parseValue coercion for built-in scalars.

Background

We initially made parseValue coercion stricter for built-in scalars to align with the JS reference implementation, and these changes were included in the v20.0 release. https://github.com/graphql-java/graphql-java/releases/tag/v20.0

Since then we've received reports that this breaking change is challenging. Although it's in line with the JS implementation, this change can potentially break clients. The plan is to provide a better migration pathway.

Progress log

Activity

  1. dondonz commented on Jul 11, 2023

    @dondonz
    MemberAuthor

    With today's release of v21.0, we're including an extra monitoring and interceptor callback for parseValue scalar coercion. See the release notes for more information: https://github.com/graphql-java/graphql-java/releases/tag/v21.0

    We'll be adding the stricter scalar coercion at some point in the future, so please make use of these callbacks to learn which incoming values will be affected. I'll close the issue for now as we have reverted the stricter coercion in v20.3 and released the migration pathway in v21.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions