dagster #announcements

schrockn

11/14/2018, 12:25 PM

and therefor hardcoded on the client

freiksenet

11/14/2018, 12:26 PM

do you mean we should do both client and server validation?

schrockn

11/14/2018, 12:26 PM

freiksenet

11/14/2018, 12:26 PM

I feel it's easier to only do server

schrockn

11/14/2018, 12:26 PM

just like how you would do with a string

freiksenet

11/14/2018, 12:26 PM

it's for linting anyway

freiksenet

11/14/2018, 12:26 PM

I don't see a reason to do it on client tbh

schrockn

11/14/2018, 12:27 PM

yeah i guess offline scenario isn’t that important

schrockn

11/14/2018, 12:27 PM

might eventually have that

schrockn

11/14/2018, 12:27 PM

with cached schema or whatever

freiksenet

11/14/2018, 12:27 PM

yeah

freiksenet

11/14/2018, 12:27 PM

I feel we can start with server side validation

schrockn

11/14/2018, 12:27 PM

just make it tolerant of server failures

schrockn

11/14/2018, 12:28 PM

so that during development

schrockn

11/14/2018, 12:28 PM

if we are stopping and restarting the graphql server

freiksenet

11/14/2018, 12:28 PM

oh yeah, it's linter anyway

schrockn

11/14/2018, 12:28 PM

👍

schrockn

11/14/2018, 12:28 PM

you see what i mean

freiksenet

11/14/2018, 12:31 PM

I want to talk about sending yaml as string for config

schrockn

11/14/2018, 12:31 PM

lol

freiksenet

11/14/2018, 12:31 PM

vs sending yaml as some other structure

schrockn

11/14/2018, 12:31 PM

was just about send that

freiksenet

11/14/2018, 12:31 PM

cause now it's relevant for validation too

schrockn

11/14/2018, 12:31 PM

what are you thinking

schrockn

11/14/2018, 12:31 PM

do you want to project into the graphql type system

freiksenet

11/14/2018, 12:32 PM

we can start with string, maybe we should project into graphql type system

freiksenet

11/14/2018, 12:32 PM

esp since yaml is implementation detail

schrockn

11/14/2018, 12:32 PM

schrockn

11/14/2018, 12:32 PM

for json

freiksenet

11/14/2018, 12:32 PM

and we might switch to some other format at some point