-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial NavigationView
implementation
#130
Conversation
Decided to try to refactor the |
It looks like SwiftWebUI uses Combine to handle the NavigationView. Is it OK to add that as a dependency? |
Yeah, sure, I have a version here tailored for SwiftWasm just for this occasion 😉 |
Also going to be handy for things such as #141 |
Turns out I didn’t end up needing it anyway! Simply overwriting the |
I merged in
Stack
|
This might be a SwiftWasm bug, I'd recommend trying with more recent (or older) snapshots, but the most recent snapshots broke SwiftPM on macOS as far as I remember. The process of picking a correct snapshot probably is going to be tedious, so maybe it would be better to wait until I get most recent snapshots fixed, IDK 🤔 |
Also, IDK if there actually is a snapshot of SwiftWasm that doesn't have this broken, would be great to isolate what exact code is actually causing this. |
Bug remains present on the latest SwiftWasm Overall, repros on:
It fails to build on |
Oh, interesting, my understanding was that SwiftPM is still broken for |
I tried it on macOS. What do you mean be SwiftPM being broken? |
I was relying on the CI logs in swiftwasm/swift#1233 in the "Run smoke tests on macOS" step, which fails with a weird error I didn't have time yet to look into. But I'm happy that it actually works, means I only need to fix the way it's used on CI, I guess. |
I sometimes get weird errors but sometimes it works just fine ¯\_(ツ)_/¯ |
Please report the errors to the main |
Sorry, I'm not sure if this PR is fully ready for review then, and if not, do you plan to address this, or maybe land that as a separate PR? |
That’s a separate issue since it also reproduces on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff, thank you so much 👏
Did some testing and it looks like the |
Probably ok to require them, unless you find it more convenient to develop and test on iOS 13/macOS 10.15. I don't have Big Sur installed and don't intend to until it's stable enough, and testing with an iOS 14 simulator is fine for me personally. @carson-katri what do you think? |
I have a machine with Big Sur, so no problems here. |
I’d rather have things working on my existing devices (13/10.15) and the AnyView stuff isn’t a huge issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great stuff and looks good to me 👍 Apologies for all the delays, but would you be able to resolve the conflicts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 🙌
NavigationView
implementation
Conflicts 🙈 |
I resolved it. Sorry, I merged App protocol before this, that's on me. |
Fixes #129.
Current status:
Destination
is visible after clicking