David Goss

IMO, for an API response here, we could go as simple as just a list of source/target pairs of node ids: ```json { "edges": [ { "source": "dataset:my-namespace:first-input", "target": "job:my-namespace:fancy-job"...

This should be solved when https://github.com/MarquezProject/marquez/pull/2620 lands as it will have the website sitting in the main repo.

This should be solved when https://github.com/MarquezProject/marquez/pull/2620 lands as it will have the website sitting in the main repo.

To recap a bit here from a discussion on Slack: - Exposing formatter implementation details is not desirable for a few reasons - cucumber-js can split out the stack trace...

@kevinlacotaco could you show an example of an XSD-compliant JUnit output with a stack trace in a property element?

Thanks for raising this @laorient. You're right that it's a bit confusing as it is. The reason we don't always include `default` is because that's the default profile and you...

> Do we really need this third source of truth? Need? No. But I think it's worthwhile (if not exactly urgent).

@Ben-EJ definitely, feel free to give this a go! I've just updated the description to clarify a 1) the prefix should be `CUCUMBER_OPTION_` to avoid collisions with env vars that...

@0v00 sure, let me know if you need any advice.

Sorry for the late reply @0v00! To your question, yes this should merge and your example is just right. For all config options we should replicate the existing behaviour (either...