Phillip Caudell @phill@mastodon.notsobig.co

There's also a sister package, GRDBQuery, which gives you a @Query property wrapper for SwiftUI (similar to @FetchRequest in Core Data)

You're then able to write views that automatically update when anything in the database changes.

Here's all the code needed for the account picker in Big Mail. So clean.

https://github.com/groue/GRDBQuery

Related: I binned off Core Data for Big Mail 2, and instead have been using the phenomenal GRDB by @groue

Not only is my app now faster and less buggy, but it’s so much easier to reason with. No weird managed contexts and elaborate dances to pass stuff between threads. Just simple, safe, Swift structs.

(Also, the documentation is INSANE) https://github.com/groue/GRDB.swift

Yeah, I write SQL queries

Xcode is now literally burnt into my display 🔥

Swipey swipe 🫵

Edit: this is swiping left on the message viewer, not tapping the List. Don't worry it's not a transition 😬

Here it is on iPhone: https://mastodon.notsobig.co/@phill/109942899530912122

And here's the rub with SwiftUI: I'm sure there are certain things I'm still doing “the wrong way”, despite doing this everyday, and reading all the docs and examples I can.

But because there have been so many genuine issues (as seen by others), my default position is “Well, the API must be broken then”. That's not a helpful mindset when debugging.

Building a low level IMAP/SMTP library has been a breeze compared to understanding how to use these APIs correctly 😅

Anyways I'm back to use NavigationLinks(value:) again, which this time seems to be behaving.

I think the reason it wasn't working last time is because I had installed a navigationDestination on my Sidebar (which is shared between compact and regular size class). It looks like it was confusing NavigationSplitView.

Now I have the navigationDestination installed just in the compact size class, and things seem okay…

Okay, another update on my Navigation Saga, because sharing is caring.

After integrating, I noticed selected rows wouldn't unselect when popping back.

Turns out using .tags() will only work if:

1) The root List is bound directly to an ObservedObject. A Binding to the same value in an ObservableObject won't work.

2) The List must only contain Text or Label views (so no pinned Grid at the top).

I'm also not sure why the Binding gets fired so many times VS the ObservedObject either? #SwiftUI

Oh. Transitions break if you multitask out of the app and back.

Commit before making huge changes

I cannot begin to tell you how down I was feeling yesterday.

Today has been has been a nice reminder that there's always a solution out there…you just might need a good night's sleep first ☺️

If there's any poor souls stumbling across this in the future, here's a gist to my solution: https://gist.github.com/phillipcaudell/085580a9412284f381a4730930c7d52f

Now to refactor this back into Big Mail 🥲 #SwiftUI

…so instead, I'm switching to a Stack when compact. Only issue is getting NavigationLink, SplitView and Stack to play together.

In the end I found it was easier to remove NavigationLinks all together, and instead use tags. Lists then use this as their selection value.

Then, using those selections, I'm computing a path to drive the Stack. Once I caught EditMode, it all worked.

No jittery toolbars. Smooth transitions. Consistent and predictable across iPhone/iPad/Mac.

Thank god.

Hallelujah! 🙌

Finally got a workaround for the NavigationSplitView regression in iOS 16.4.

Transitions stop working when the content column no longer contains a List (say you have a “Select Mailbox" view, a Grid, etc).

Here's a gist of the issue: https://gist.github.com/phillipcaudell/6d4d0efac6a22cd42bf75f3acd7a033b

It seems to suddenly start behaving like a NavigationStack, which is why adding a navigationDestination sorta works (except now you've got wonky nav animations, and it still sometimes fails)…

Well hot damn, someone on Twitter suggested setting the Set's underlying type to Optional, and voila, editing and navigation!

I'm still not entirely sure why this works though. Surely an empty Set would denote no selection? Making the type itself Optional isn't intuitive at all.

Even the init signature doesn't give any hints, only that the Binding itself can be Optional... 🤷‍♂️ #SwiftUI

Okay one for the #SwiftUI crowd: Do we have a definitive answer whether a List's selection binding should be Identifiable or not?

Apple seem to play fast and loose with this. Some of their example projects (Food Truck) don't conform to Identifiable, and the Swift header for List only has Hashable as the requirement. Meanwhile the docs say a List's selection should conform to Identifiable.

So what is the truth? What do you do in your apps?

I refuse to sleep until I have found a solution to this, which is unfortunate, as it means I may never sleep again 🥲

I've now officially arrived in crazy town, and started wrapping UINavigationController myself.

What's interesting is that the SwiftUI environment is still automatically adding nav items to the controller, so I've actually got the same broken animations as with NavigationStack. At least it’s…consistent.

Running out of ideas now 😅

Okay, so by adding a .navigationDestination(for:) to the sidebar column, it fixes the content to detail column animation.

However, now the sidebar to content column animation is broken. I've tried fiddling around with .navigationBarTitleDisplayMode(.large), etc. Nada.

I need to lay down.