Should note that we are removing tests for rendering the type page, solids page, and playground. But let's burn it down. Curious to see what testing structure you have in mind...
Thu, Oct 29
I'm working on a nicer way to surface these errors in the UI, but as part of the overall nav structure changes.
Wed, Oct 28
Tue, Oct 27
This looks good to me - I guess it replaces the MockedProvider we already have in place in App.test.tsx?
I think that our current implementation of the graphql mocking is a bit unusual but it was designed to replace defaultMocks with query results loaded from a folder of JSON files. (At the time, Apollo seemed to suggest maintaining "defaultMocks" by hand, and for our queries that'd be crazy.) The current setup allows you to run the actual GraphQL server and pull down real data to generate the folder of mocks, and then run the tests against those files. It's definitely not ideal because changes to the demo pipelines change the GraphQL mocks which change the snapshots, but it seemed like maintaining the mocks by hand was untenable.
Mon, Oct 26
+bengotow, went with a dir for sample data because ts didn't like the .data.ts extension
Fri, Oct 23
Thu, Oct 22
Clean up border-radius on tag value
Tue, Oct 20
I'm a little bit worried that the whole concept of a repo location isn't necc. clear to users right now though, especially when they only have a single repository in each location
Mon, Oct 19
Possibly crazy idea: can we use a yaml CodeMirror here? E.g.
Direction looks great to me. Some nits inline, mostly stylistic/legibility things.
Fri, Oct 16
Remove rogue console.log
Thu, Oct 15
Show 'Snapshot' if there is no current pipeline state
Wed, Oct 14
Tue, Oct 13
Some minor comments -- the only one that strikes me as a maybe-bug is the pop followed by slice.