Preview Providers now compile correctly

[Tyler-Keith-Thompson]

Linked Issue: Closes #156

Checklist:

• [x] Did you sign the Contributor License Agreement?
• [x] Is the linter reporting 0 errors?
• [x] Did you comply with our styleguide?
• [x] Is there adequate test coverage for your new code?
• [x] Does the CI pipeline pass?
• [x] Did you update the documentation?
• [x] Did you change the public API?
• [x] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

---

If Public API Has Changed:

• [ ] Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
• [x] Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
• [x] If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

[codecov-commenter]

Codecov Report

Merging #160 (4e67408) into main (3097cea) will decrease coverage by 0.07%. The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #160      +/-   ##
==========================================
- Coverage   91.27%   91.20%   -0.08%     
==========================================
  Files          92       92              
  Lines        2373     2353      -20     
==========================================
- Hits         2166     2146      -20     
  Misses        207      207              

Impacted Files	Coverage Δ
...ent_SwiftUI/Extensions/ThenProceedExtensions.swift	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 9c97271...4e67408. Read the comment docs.

[Tyler-Keith-Thompson]

Some notes:

• We tried to use deprecations and the rename availability attribute however XCode 13.2.1 refused to be smart enough to pick the new global method.
• There is a breaking change in here. You used to be able to call self.thenProceed, which referred to a local method. Now that the method is global and the local methods are removed this no longer works and results in an error. @morganzellers what do you want to do about that?
• It's possible for somebody to include this in UIKit and get some funky behavior because they forgot to put a . for their UIKit thenProceeds. This can result in some really undesirable behavior especially if they just use fix from xcode without paying attention (screenshots attached) Step 1: Mistype, note that this auto-imports SwiftCurrent_SwiftUI which is "helpful"

  Step 2: Notice an error and click

  

  Step 3: Erroniously believe Xcode has your back and fix the comma

  

  Step 4: Erroniously believe Xcode has your back and fix the args

  

  Step 5: Have a workflow with 1 screen that launches with arguments of a WorkflowItem and a secondary screen which will never show.

  

[morganzellers]

• There is a breaking change in here. You used to be able to call self.thenProceed, which referred to a local method. Now that the method is global and the local methods are removed this no longer works and results in an error. @morganzellers what do you want to do about that?

I think we should version bump then. Does this force us to do a major version bump, or could we get away with bumping to v4.6.0?

[morganzellers]

I feel like I'm okay just gating this for our next version bump. It feels far away, but this isn't worth bumping to 5.0 now

[Tyler-Keith-Thompson]

Agreed. Should we create a 5.0 branch and merge it there?

[morganzellers]

Agreed. Should we create a 5.0 branch and merge it there?

I like that idea, I can do that