GC Status checks subscription queries against current types, instead of future types #465

schickling · 2017-09-08T09:35:32Z

Issue by do4gr
Friday Sep 08, 2017 at 09:24 GMT
Originally opened as https://github.com/graphcool/api-bugs/issues/271

When validating a local project with gc status it checks subscription queries against the current project state instead of the future state including the type changes. GC deploy already does the correct thing. They both should do the correct thing.

do4gr · 2017-09-14T08:38:54Z

This is fixed now. Tested for deploy and diff commands now.

schickling added this to the 1.4 milestone Sep 8, 2017

schickling added area/local-workflow and removed area/local-workflow labels Sep 8, 2017

sorenbs added component/engine/system-api bug/2-confirmed and removed component/engine labels Sep 8, 2017

marktani changed the title ~~GC Status is not running the same Validations as GC Deploy~~ GC Status checks subscription queries against current types, instead of future types Sep 11, 2017

do4gr closed this as completed Sep 14, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GC Status checks subscription queries against current types, instead of future types #465

GC Status checks subscription queries against current types, instead of future types #465

schickling commented Sep 8, 2017

do4gr commented Sep 14, 2017 •

edited

GC Status checks subscription queries against current types, instead of future types #465

GC Status checks subscription queries against current types, instead of future types #465

Comments

schickling commented Sep 8, 2017

do4gr commented Sep 14, 2017 • edited

do4gr commented Sep 14, 2017 •

edited