https://dagster.io/ logo
Powered by
#announcements
  • b

    Ben Gotow

    11/30/2018, 2:16 AM
    that’s awesome
  • s

    schrockn

    11/30/2018, 2:16 AM
    that was fucking magical
  • s

    schrockn

    11/30/2018, 2:16 AM
    like basically worked on the first try
  • s

    schrockn

    11/30/2018, 2:16 AM
    one of those
  • b

    Ben Gotow

    11/30/2018, 2:16 AM
    oh man love that feeling
  • s

    schrockn

    11/30/2018, 2:16 AM
    i yelled. my wife was confused.
  • b

    Ben Gotow

    11/30/2018, 2:36 AM
    haha the joys of programming
  • b

    Ben Gotow

    11/30/2018, 2:37 AM
    I’ve got this YAML formatting working better - recognizes nesting of inline dicts as well as standard dicts, and the suggestions only includes unused keys
  • b

    Ben Gotow

    11/30/2018, 2:37 AM
  • s

    schrockn

    11/30/2018, 2:37 AM
    sweet
  • s

    schrockn

    11/30/2018, 2:37 AM
    i’m so ignorant about yaml that i didn’t even know about the alternative dictionary format
  • s

    schrockn

    11/30/2018, 2:37 AM
    good thing since all programming will be in yaml files in 10 years at this rate
  • b

    Ben Gotow

    11/30/2018, 2:37 AM
    gotta feed it some exhaustive yaml and make sure I didn’t break anything but getting there.
  • b

    Ben Gotow

    11/30/2018, 2:38 AM
    haha i know I didn’t realize this was a thing until I read the parser
  • s

    schrockn

    11/30/2018, 2:38 AM
    useful for leaf nodes
  • b

    Ben Gotow

    11/30/2018, 2:39 AM
    yeah I agree
  • b

    Ben Gotow

    11/30/2018, 2:39 AM
    ahh brb gotta get some dinner
  • s

    schrockn

    11/30/2018, 2:40 AM
    cool
  • s

    schrockn

    11/30/2018, 2:40 AM
    ttyl
  • b

    Ben Gotow

    11/30/2018, 5:08 AM
    well looks like I broke some yaml parsing… haha gotta handle some edge cases
  • b

    Ben Gotow

    11/30/2018, 6:10 AM
    hey also @freiksenet when you get a chance—for the config evaluation errors in the graphQL schema
  • b

    Ben Gotow

    11/30/2018, 6:10 AM
  • b

    Ben Gotow

    11/30/2018, 6:11 AM
    where you thinking we’d just use the stack instead of the path? (since it seems to also contain the path to the offending yaml node via 
    EvaluationStackPathEntry
    )
  • b

    Ben Gotow

    11/30/2018, 6:24 AM
    gonna fix the highlighting of errors in the yaml editor tomorrow
  • f

    freiksenet

    11/30/2018, 7:11 AM
    path is legacy, just remove
  • f

    freiksenet

    11/30/2018, 7:11 AM
    @Ben Gotow we should use stack, path is there cause I've assumed the api would be like that, it should be removed
    👍 1
  • f

    freiksenet

    11/30/2018, 10:04 AM
    I'd actually want something like a monad right now
  • f

    freiksenet

    11/30/2018, 10:05 AM
    so that I could do smth like
  • f

    freiksenet

    11/30/2018, 10:05 AM
    getRepositoryOrError >== getPipelineOrError >== validateOrError >== doSMth
  • s

    schrockn

    11/30/2018, 1:05 PM
    yeah that would be good @freiksenet
1...747576...185Latest