@MatManferdini It should be @.ViewBuilder var accessory: Accessory and it will auto-generate an init that takes a closure, executes it and stores it in the var. Which is the correct pattern for data dependencies.
@MarwahaArihant@CarlosBBuild i use var id { ObjectIdentifier(self) } since the default id implementation changes between insert and save which screws up list animations.
SwiftUI Tip ๐ก
In iOS 26.0+, use labelReservedIconWidth() to give labels a consistent icon width.
This keeps text aligned even when icons have different sizes.
@alpennec "If people have unsaved changes in the sheet when they begin swiping to dismiss it, use an action sheet to let them confirm their action." double sheets???
@bazzaclem@virginmedia If you use their whatsapp chat bot and choose cancel itโll offer a new customer contract pricing probably a bit lower than ยฃ26.99 but contacts are now 2 years (They say to save you having to use the chat bot every year but I donโt find it that much of a hassle!)
@twannl@NilCoalescing A few mistakes there. @.State should not init objects its like a heap memory leak. async func should not be in class, if called twice it will corrupt any of the class's properties. Async funcs should return a result that is set on the @.State instead.
@ScotRail prize for most annoying thing ever is this pointless Wi-Fi survey no body is going to fill in accurately since it's asked every station every day: