CombineNavigation package for UIKit

[maximkrouk]

Finally finished implementing core logic for https://github.com/capturecontext/combine-cocoa-navigation

I still need to finish the example, cleanup/improve readme and docs, but existing tests are passing and simple example seems to work perfectly.

Hope to release 1.0.0 by the end of this year, so if someone finds time to play with it before the release, I would love to hear your feedback ❤️

Lets make TCA with UIKit great at the first time 😁

[maximkrouk]

Created observation-beta branch in composable-architecture-extensions and updated https://github.com/capturecontext/combine-cocoa-navigation example using extensions package

The example is yet pretty basic, but now navigation API is tailored for TCA, not just Combine

[maximkrouk]

Some observation-beta feedback:

---

I noticed that @ObservableState does not support typealiases like

@ObservableState
typealias State = IdentifiedArrayOf<OtherFeature.State>

That's kinda unfortunate, but don't see how it can be implemented since macro needs to add some props to the declaration 💁‍♂️

---

@Reducer adds @CasePathable macro to Action but doesn't add @ObservableState to State, not sure if it was intended by design, but confused me a little, I may create a PR if it's a bug 🫠

---

@stephencelis @mbrandonw observation-beta discussion is closed and the feedback feels too minor to create a separate discussion, so I decided to provide it here 🌚

[mbrandonw]

Hi @maximkrouk, definitely feel free to open a new discussion. It's easier for us to track than adding it to an unrelated thread.

I noticed that @ObservableState does not support typealiases like

That is just a limitation of macros, and the same is true of @Observable. Also, IdentifiedArray is not observable.

@Reducer adds @CasePathable macro to Action but doesn't add @ObservableState to State, not sure if it was intended by design, but confused me a little, I may create a PR if it's a bug 🫠

It's a purposeful omission for now. Suddenly adding @ObservableState to everyone's state has huge ramifications. It will lead to over observation of state when mixed with WithViewStore, and it will lead to lots of runtime warnings telling people that they need to wrap their views in WithPerceptionTracking for iOS <17 support.

Once we can fully remove the concept of ViewStore from the library and force everyone to use @ObservableState, then we can have @Reducer automatically apply the macro.

[maximkrouk]

Definitely feel free to open a new discussion. It's easier for us to track than adding it to an unrelated thread.

Ok, I'll be creating new discussions if I find smth else to share 👌

That is just a limitation of macros, and the same is true of @observable

Yeah kinda makes sense 🫠

It's a purposeful omission for now. .....

Thank you for clarification 👍

[maximkrouk]

Just watched available ObservableArchitecture episodes, very cool step-by-step guide on "hows and whyes" of most recent changes in the repo ❤️