Editing SwiftData model objects - SwiftData SwiftUI Tutorial 1/5

Download the completed project here: github.com/two...
Other parts in Project 12:
Introduction: www.hackingwit...
1. Editing SwiftData model objects: This video
2. Filtering @Query using #Predicate: • Filtering @Query using...
3. Dynamically sorting and filtering @Query with SwiftUI: • Dynamically sorting an...
4. Relationships with SwiftData, SwiftUI, and @Query: • Relationships with Swi...
5. Syncing SwiftData with CloudKit: • Syncing SwiftData with...
Wrap up and challenges: www.hackingwit...
You can find the full set of videos, along with transcriptions, challenges, tests, and more, in my free 100 Days of SwiftUI course: www.hackingwit...
Watch the full 100 Days of SwiftUI playlist here: • Understanding the basi...

[@DominikButz]

🎉Great tutorial, thanks Paul. I hope you will show cloudkit integration with SwiftData in one of the next videos, too. In my experience, most tutorials about SwiftData skip this part. However, most production apps using core data (and in the future SwiftData) can’t do without cloudkit sync.

[@OttoFaerber]

Swiftdata is only easier than coredata for very simple data.
As soon as you want to go into the cloud, things are much more complicated.

[@congtuhuyet5502]

Let me ask a stupid question, is using cloudkit sync a mandatory policy if you use SwiftData when upload your app to the appstore?

[@OttoFaerber]

@@congtuhuyet5502 no

[@heestand_xyz]

Clean and quick tutorial, thanks!

[@clemensauer8597]

Your link in description opens CoreData Introduction, not SwiftData one.

[@nroose]

Seems like "transparent" is the wrong word (at about 2:58). Transparent would mean we can see how it works. It is invisible to us, not transparent.

[@LebenWerden]

Hello, App runs in the simulator but not in the Xcode preview.
Why?

[@barrywest3270]

I am a new Swift Developer. I have coded the project as in the video and doubled checked the coding. I have no compile errors but the completed project runs but no User Screen ( Content View) displays and no errors show in the debugger. I simple show a blank white screen with no Heading Users in the Top Left of the IPhone Screen. I am using IOS 17.2 Minimum Deployments. In the debugger it appears to be related to the @Environment on line 13. It I set a break point there and it never goes into the view body. Where might I have an error? Thanks

[@barrywest3270]

Found a typing error. had a } out of sync and caused the error. the closure prevented the code execution.

[@nroose]

Newbie question: Does everyone just hit return after typing each line to get the autocomplete to go away and then get to the next line? Just find it really annoying.

[@youngdomsey]

Yes I do that. How would you expect it to work or is that question already outdated since you asked 6 months ago and you are probably more experienced now 😊

[@nroose]

@@youngdomsey There are a bunch of ways in different editors and text entry environments do auto-complete. I prefer using tab for autocomplete. I guess that is left over in my muscle memory from Unix and then Linux terminal which I have been using for 30 years. I think that was the original auto complete. Most environments don't really do that. I am still having trouble getting past that moment when I have typed in what I want to type in and that is one of the options but there are others and it's the end of the line, and sometimes I hit return and start typing the next line, but at that same moment xcode is bringing up the autocomplete and instead of going to the next line, it just selects and stays there.

[@youngdomsey]

@@nroose ok I see. Yeah sometimes I think that it would be faster if I would type more and use completion less. Personally I also sometimes use tab when I jump between these prefilled parameters of an init for example 😊
Everybody does it slightly different I guess.