[DNM WIP] SwiftUI testbed app - #240
square-tomb wants to merge 28 commits into
Conversation
fc64963 to
52f9c04
Compare
This reverts commit ccbec00.
n8chur
left a comment
There was a problem hiding this comment.
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.
|
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! |
invert modal and Market containers Co-authored-by: Westin Newell <westin@squareup.com>
Co-authored-by: Westin Newell <westin@squareup.com>
Co-authored-by: Westin Newell <westin@squareup.com>
@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. |
665c9bc to
4942daa
Compare
Done! |
…ftui-testbed * 'main' of github.com:square/workflow-swift: Add WorkflowSwiftUIExperimental (#252) Add convenience method for library definitions to reduce boilerplate (#251) [release]: bump to version 3.4.0 (#250) RxSwift 6.6 (#212) Expose 'screen' on WorkflowHostingController (#246) [fix]: address some RenderTester limitations with optionals (#245) Resolved Swift 5.9 compilation warning related to UnsafeRawPointer object conversion (#243) Bump activesupport from 6.1.7.3 to 6.1.7.6 (#242)
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
The
--verbosehere is to makepod gen's progress visible, because it may take several minutes to download Market pods. ThenWith the project open in Xcode, select the target
Development-SwiftUITestbedto build and run.Links