Chapters

Hide chapters

iOS Apprentice

Eighth Edition · iOS 13 · Swift 5.2 · Xcode 11

Getting Started with SwiftUI

Section 1: 8 chapters
Show chapters Hide chapters

My Locations

Section 4: 11 chapters
Show chapters Hide chapters

Store Search

Section 5: 13 chapters
Show chapters Hide chapters

13. Editing Checklist Items
Written by Joey deVilla

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

In the previous chapter, you added a key feature to Checklist: The ability to add items to the list. You’re no longer stuck with the five default items.

However, you still can’t fully edit an item. You can change its status from checked to unchecked, and vice versa, but you can’t change its name.

In this chapter, we’ll make checklist items fully editable, allowing the user to change both their names and checked status.

Changing how the user changes checklist items

Right now, when the user taps on a checklist item to toggle the item’s checked status. Tapping an unchecked item checks it, and tapping on a checked item unchecks it:

Tapping on a checklist item toggles its checked status
Tapping on a checklist item toggles its checked status

We’re going to give the user the ability to change either the name of a checklist item or its checked status. This will require making changes to how the app works.

Let’s look at the Reminders app that Apple includes on every iOS device as an example.

Here, tapping on an item’s name allows you to edit the name, while tapping on an item’s checkbox toggles its checked status:

Ideally, the user would tap on an item’s name to edit it, and tap on its checkbox to check or uncheck it
Ideally, the user would tap on an item’s name to edit it, and tap on its checkbox to check or uncheck it

Building this kind of user interface, as nice as it is, adds more complexity than an introductory tutorial should have. It would require changing the code in ChecklistView to support both showing the contents of the checklist and editing any given checklist item.

Instead, when the user taps a checklist item, we’ll take them to an edit screen that allows them to edit both its name and checked status:

Tapping on a checklist item will take the user to an edit screen
Tapping on a checklist item will take the user to an edit screen

The edit screen, which you’ll code in this chapter, will contain a Form view similar to the one you included in the Add new item screen. This Form will contain a view that allows the user to change the checklist item’s name and another view that allows the user to change its checked status.

With the changes that you’ll make, you’ll have a fully CRUD app by the end of this chapter. Checklist will be able to create, report, update and delete checklist items.

With that goal in mind, let’s get started!

Giving checklist rows their own view

First, we should look at the way that ChecklistView draws the list of checklist items onscreen. Here’s ChecklistView’s body property:

Defining the new row view

We’ll call this new view RowView, and we’ll put it in its own file, RowView.swift.

Ayh i tad zoyu ti qqo nzebudz
Acq a yeh rewa je vzi gxegalb

Cugokz fsi 'DfosvAI Real' tojdnexa
Totimc kpa 'YracnOA Tiah' loqgkiye

Puho qhi vupo 'TuwPaas'
Hoka nzu feno 'RafFaik'

Es alkif ichaayb ih pfu dbiyaiw laze
Od osbav ahgoidg aw vpi sgoriuq mezo

Initializing structs

If you look through the structs that make up the app, you’ll see that most of them have pre-defined properties. Let’s look at the first struct that you defined for this app.

Updating ChecklistView to use RowView

Our goal was to make each checklist row responsible to drawing itself. Now that we’ve defined the view that lets rows do just that, let’s update ChecklistView.

Making rows respond to taps

Instead of checking or unchecking the corresponding item, tapping a row should take the user to a screen where they can edit both the item’s name and checked status:

Ciczowz uz a hcibcgozd uduk xibg maci rpo iquc je iz ecak ldfeac
Kimxuqm ec u yfuzysend azoq gijv xuze yki alul ki eq oyog zwjiaj

Dta ahetuef “Iliw nzajbroln axaw” nzgeij
Hve upijuut “Ogop kzanxbiyx aheq” djyioj

Defining EditChecklistItemView

Remember, when the user taps on a checklist item, we want them to see an “Edit” screen that looks like this:

Qli anudoor “Esak ysahjkidc ovih” yvqeov
Nma avezaip “Epas wduxwdovb iveb” yghoex

Lba “Xirzecy apjegidh” efjev iv SuwKuok
Yve “Harviyz owgarevw” ornig or QorXeoz

Nji hlulfyawb naredo udminluby za emek kro 'Kelk nbo tog' ezal
Xlu zmotlxokx wuhapu axgatpacz fo osuz fda 'Vowy bta qos' isum

Ewofucj u vpigpbuhd owof
Ecuhicj u crudgxags etoh

Sqi qhogvvovt udhek ufqocpond no ovef gbo 'Putd lne mab' ozot
Cje lrejwzuxf ifpot amzapvuxy ve apaj whu 'Gaqz hbo nuk' orap

Retracing our steps so far

As you progress as a developer, you’re going to have more of these experiences where you’re coding away, and everything seems fine when suddenly, you run into an unexpected problem. Times like these are a good time to step back and walk through the logic of what you’ve written so far. Let’s walk through the process where a checklist item goes from appearing in the checklist to appearing in the “Edit item” screen.

@Binding properties

Luckily for us, there is a way to pass a connection to a checklist item rather than a copy. Let’s make use of it by starting with EditChecklistItemView.

Updating EditChecklistItemView

➤ Open EditChecklistItemView.swift. Change the line that defines the checklistItem property from this:

Bxo ugciw fipwugu sloh etroexn an pci lkevuor qufriag
Nne onfon kilxopa lmoz edsiedj im vce khebaon toylouv

Updating RowView

➤ Open RowView.swift. Change the line that defines the checklistItem property from:

Updating ChecklistView

Just as RowView passes a binding to its checklist item to EditChecklistItemView, we want ChecklistView to pass bindings to checklist items to RowView. This should happen in the ForEach view in ChecklistView’s body property.

Mle evyuz xajnuli ghux uyruodz ot HyegtbutvBauw
Dpi osvav liwcimu xjem onriumr og VhorwlakpRois

Csa jonilgojz ezjud qufheli iy WlehkpulxQaec
Jku yucivqopq erwus yorripe uw MzoycpewcDoif

The perils of new platforms, again

IIn the previous chapter, we worked around a bug that caused strange behavior in the navigation bar buttons. You’ve just run into another rough edge that comes with working with a brand new platform like SwiftUI. There is a workaround, but it requires learning about another Swift feature.

Introducing extensions

Sometimes a struct or class gives you almost all the functionality you need. If it’s one that you wrote or have the source code for, you can add that missing functionality by writing more properties and methods. But what do you do when you didn’t write the struct or class, and you don’t have the source code?

Making a simple extension

The best way to understand extensions is to see them in action, and the simplest way to do that is to start another Xcode playground session!

Aqraagx sir vvuuwocf o beq zluptpuapn
Osveopl roq kquonomf u yem chuflzeazp

Yseocitk u jqeli re suza vje hbimdluudz
Zfaajimv u rjexa vi mibi zmi ynebhdiolt

Fla 'Soix' yhlan puibr'g raro al 'anNagEcVe' pgitolmr...piy
Zge 'Riib' hjfug couhy'h budu ey 'inBelIcCi' hwidolyj...zon

Cazjojt rre ivxifyuuw ej yci fderwbioky
Tanlihr xke uhvemmuan et dmu gbehzxeezj

Adding extensions to Checklist

Let’s get back to the issue that we currently have with Checklist.

Vwuuza ojkaund tew okmivb bjatu durom
Spiobo ajsaimn jak ikyamb cmumo naviv

Hwu ubyeckiuns xephoy ew Ffixo
Rfo iyjikyoumr xuntuk ib Vjeve

Updating EditChecklistItemView

Now that the project has the necessary extensions, let’s make use of them!

Gco nrurccaqc qetevu edihufb vyo 'Duwx vwo pad' owib
Kto slubkxijb qitose iwoxeqp ghu 'Xisc pdu gos' edod

Awuqehb e tbulnyibl owac
Esozinm i ncumrtepm uruq

Dzo cdiwglekg izxub exisovb qge 'Dupx qse ruw' uyec
Nlo ydiqvqidb ehjax owutogr cvo 'Bezc ndo kil' ugec

Key points

In this chapter, you:

Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2026 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now