graphql-schema_comparator icon indicating copy to clipboard operation
graphql-schema_comparator copied to clipboard

Nuance to EnumValueAdded's criticality

Open cjoudrey opened this issue 6 years ago • 1 comments

At the moment, all EnumValueAdded changes are marked as dangerous because it may break clients that do not handle a certain enum value.

This is true if you're using the enum as a field type, but if you're only using it as an argument type, adding a new enum value should be safe.

cjoudrey avatar Jun 06 '18 20:06 cjoudrey

Similarly should removing an enum value for enums only used in field types and not argument types be safe? In that case, the enum value should never appear in a client request so I don't think it could break anything.

jturkel avatar Aug 04 '21 16:08 jturkel