Skip to content

All inputs that expect an ID (global or integer) should be of Type ID in the Schema #997

Open
Open
All inputs that expect an ID (global or integer) should be of Type ID in the Schema#997
Labels
compat: breaking changeThis is a breaking change to existing functionalitycomponent: inputRelating to GraphQL Input Typeseffort: highMore than a weekimpact: medMinor performance improvements, fix broad user base issuesobject type: commentRelating to the Comment Typeobject type: postRelating to the Post Object Typesobject type: termRelating to the Term Typesobject type: userRelating to the User Typestatus: actionableReady for work to begintype: enhancementImprovements to existing functionality
Milestone
v3.0
@jasonbahl

Description

@jasonbahl
jasonbahl
opened on Nov 3, 2019

We're breaking #109 into 2 issues.

This issue should address making all input Types that expect an ID of some sort to be of Type ID.

Resolution can still be inconsistent (for now), but the Schema itself should all be of Type ID so that we can make resolution consistent in the future.

Metadata

Metadata

Assignees

No one assigned

    Labels

    compat: breaking changeThis is a breaking change to existing functionalitycomponent: inputRelating to GraphQL Input Typeseffort: highMore than a weekimpact: medMinor performance improvements, fix broad user base issuesobject type: commentRelating to the Comment Typeobject type: postRelating to the Post Object Typesobject type: termRelating to the Term Typesobject type: userRelating to the User Typestatus: actionableReady for work to begintype: enhancementImprovements to existing functionality

    Type

    No type

    Projects

    WPGraphQL Issue Triage

    Status

    🛑 On Hold

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions