[DNM WIP] SwiftUI testbed app

[square-tomb]

A sample app designed for trying out approaches to porting Blueprint screens in a Workflow-driven app to SwiftUI.

I had found rewriting parts of the TicTacToe sample app to be of limited value due to the app’s simplicity and differences from Square's actual product code.

This should not be merged as it depends on Square internal libraries.

How to use

In the top-level directory, run

bundle install
be pod gen --verbose

The --verbose here is to make pod gen's progress visible, because it may take several minutes to download Market pods. Then

open gen/Development/Development.xcworkspace

With the project open in Xcode, select the target Development-SwiftUITestbed to build and run.

Links

• [RF-9056] Workflow SwiftUI testbed app - Jira

[n8chur]

This looks like a great start for a test bed in which we can add new scenarios to test as we come up with them!
I'll try to take another more thorough pass before our call and try to come up with additional scenarios.

[n8chur]

It might also be nice to have a ProxyElement defined that creates a reusable component with an associated stylesheet involved here since that's a relatively common pattern that we'll want to also migrate. I don't think it's necessary from a Workflow standpoint, but if we're trying to test out what a conversion looks like it'd be nice to include!
I can help abstract a shared component if you'd like, but you can find info on how to do so yourself here: https://www.notion.so/marketdesignsystem/Making-Custom-Components-74370084ed354456860cb307c76a7bc5

[square-tomb]

It might also be nice to have a ProxyElement defined that creates a reusable component with an associated stylesheet involved here since that's a relatively common pattern that we'll want to also migrate… I can help abstract a shared component if you'd like…

@n8chur Per our conversation today, I'll take you up on adding/extracting that component! Feel free to push commits directly to this branch. I'll avoid rebasing from here on out.

[n8chur]

It might also be nice to have a ProxyElement defined that creates a reusable component with an associated stylesheet involved here since that's a relatively common pattern that we'll want to also migrate… I can help abstract a shared component if you'd like…

@n8chur Per our conversation today, I'll take you up on adding/extracting that component! Feel free to push commits directly to this branch. I'll avoid rebasing from here on out.

Done!