3.0 Release (#689)

.gitignore

@@ -23,4 +23,7 @@ DerivedData
 *.xcscmblueprint
 
 # SPM
-.build/
+.build/
+
+# DocC
+.docc-build

CKWorkspace.xcworkspace/xcshareddata/swiftpm/Package.resolved

@@ -1,16 +1,32 @@
 {
-  "object": {
-    "pins": [
-      {
-        "package": "FHIRModels",
-        "repositoryURL": "https://github.com/apple/FHIRModels.git",
-        "state": {
-          "branch": null,
-          "revision": "31dc40c01ef43b89191be5d9719e1ddedb2c91b5",
-          "version": "0.1.0"
-        }
+  "pins" : [
+    {
+      "identity" : "fhirmodels",
+      "kind" : "remoteSourceControl",
+      "location" : "https://github.com/apple/FHIRModels",
+      "state" : {
+        "revision" : "e115442fb3c5d44ffb1dc9b4e039b77fd143ad96",
+        "version" : "0.4.0"
       }
-    ]
-  },
-  "version": 1
+    },
+    {
+      "identity" : "swift-async-algorithms",
+      "kind" : "remoteSourceControl",
+      "location" : "https://github.com/apple/swift-async-algorithms",
+      "state" : {
+        "revision" : "aed5422380244498344a036b8d94e27f370d9a22",
+        "version" : "0.0.4"
+      }
+    },
+    {
+      "identity" : "swift-collections",
+      "kind" : "remoteSourceControl",
+      "location" : "https://github.com/apple/swift-collections.git",
+      "state" : {
+        "revision" : "937e904258d22af6e447a0b72c0bc67583ef64a2",
+        "version" : "1.0.4"
+      }
+    }
+  ],
+  "version" : 2
 }

CareKit.xctestplan

@@ -99,7 +99,6 @@
     }
   ],
   "defaultOptions" : {
-    "codeCoverage" : false,
     "targetForVariableExpansion" : {
       "containerPath" : "container:CareKit.xcodeproj",
       "identifier" : "8605A5B91C4F04EC00DD65FF",
@@ -111,7 +110,7 @@
       "target" : {
         "containerPath" : "container:CareKit.xcodeproj",
         "identifier" : "5196C7F8226F8F8F00F1C2A2",
-        "name" : "CareKitTests iOS"
+        "name" : "CareKitTests"
       }
     }
   ],

CareKit/CareKit.docc/CareKit.md

@@ -0,0 +1,21 @@
+# ``CareKit``
+
+CareKit is an open source framework that you can use to build apps to manage and understand health data. Apps can highlight trends, celebrate goals, and create incentives for users. CareKit makes it easy to provide engaging, consistent interfaces with delightful animations, and full interaction with the accessibility features of iOS and iPadOS.
+
+## Overview
+
+This open source framework is written entirely in Swift, and leverages some of the most powerful Swift language features.
+
+Your CareKit apps can:
+
+- Easily digitize a prescription.
+
+- Provide meaningful health data and trends to users.
+
+- Allow users to connect with their care providers.
+
+The framework provides a powerful set of data models for persistence. Your app’s user is represented in CareKit’s data as a patient. A patient needs to complete a set of tasks, like taking a medication or logging their symptoms. Create tasks with a schedule so that patients know when to perform each task. Schedules are composable, so you can build a complex set of requirements by combining simple ones.
+
+The combination of a patient’s tasks make up a care plan. A care plan helps a user improve part of their health; for example, recovering from an operation or managing diabetes. A patient can have multiple care plans, and each care plan can have contacts associated to them. Contacts are the patient’s care providers.
+
+When a patient completes a task, CareKit stores results as outcomes. These outcomes and their associated values enable you to provide charts and graphs for a user to help them understand the health impact of their care plan.

CareKit/CareKit.docc/Resources/Creating and Displaying Tasks for a Patient/Creating and Displaying Tasks for a Patient.md

@@ -0,0 +1,114 @@
+# Creating and displaying tasks for a patient
+
+Create tasks and schedules for patients and display them using a synchronized view controller.
+
+## Overview
+
+When creating an app using CareKit, you can create tasks, such as taking medication or performing an exercise, for the user to complete. To create tasks for users, first create a store. This provides a place for your task data to persist. Then create both simple and complex task schedules so your users know when to perform their tasks. You can then present the scheduled tasks to the user.
+
+### Create a store
+
+Create a store for your data. You instantiate your store with a name. There’s no specific validation of this name, but it’s good practice to make it distinctive. Use the reverse-url format bundle identifier of your app with a unique name appended:
+
+```swift
+import CareKit
+import CareKitStore
+
+let storeName = "com.mycompany.myapp.nausea"
+let store = OCKStore(name: storeName) 
+```
+
+If you attempt to create a store with a name of an already-existing store, the `OCKStore` initializer returns the existing store.
+
+### Create a schedule
+
+When creating a task, provide a schedule so users know when they need to complete the task. For a task like taking a medication, the schedule specifies when the user should take that medication, such as 11:00 AM or after dinner.
+
+You build schedules by defining times, offsets from known times, and ranges across times and dates that consists of at least one schedule element. A schedule element represents a defined moment or range of moments.
+
+> Note: Calendar calculations are complex and depend on the user’s device settings for time zone and calendar. Use the provided Calendar API for the Date and DateComponents to simplify this.
+
+Building a schedule takes a few simple steps. The code below shows how to create a schedule that occurs every day at 8:00 AM, starting on the current day. In the first line, Calendar returns the first moment of today’s date based on the user’s calendar. In the second line, add 8 hours to create a date object at 8:00 AM. Next, create a schedule element, using today’s date at 8:00 AM, then set it to occur daily. In the last line, create a schedule using the schedule element you created in the line before.
+
+```swift
+let startOfDay = Calendar.current.startOfDay(for: Date())
+let atBreakfast = Calendar.current.date(byAdding: .hour, value: 8, to: startOfDay)!
+
+let dailyAtBreakfast = OCKScheduleElement(start: atBreakfast, end: nil, interval: DateComponents(day: 1))
+
+var schedule = OCKSchedule(composing: [dailyAtBreakfast])
+```
+
+Create your schedule using date objects initialized with the user’s calendar preference. There are a variety of calendars your user could be using, each with different properties and nuances. Creating dates with the user’s calendar preference ensures correct date calculations.
+
+### Schedule multiple elements
+
+If you need a schedule that’s more complex than listing once-a-day events, you can build it by working with multiple schedule elements. The code below expands on the previous code example by creating an additional schedule element that occurs every other day at 12:00 PM. Finally, it creates a schedule with the two schedule elements.
+
+```swift
+let startOfDay = Calendar.current.startOfDay(for: Date())
+let atBreakfast = Calendar.current.date(byAdding: .hour, value: 8, to: startOfDay)!
+
+let dailyAtBreakfast = OCKScheduleElement(start: atBreakfast, end: nil, interval: DateComponents(day: 1))
+
+let atLunch = Calendar.current.date(byAdding: .hour, value: 12, to: startOfDay)!
+
+let everyTwoDaysAtLunch = OCKScheduleElement(start: atLunch, end: nil, interval: DateComponents(day: 2))
+
+var schedule = OCKSchedule(composing: [dailyAtBreakfast, everyTwoDaysAtLunch])
+```
+
+### Create and save tasks to the store
+
+Once you’ve defined a schedule, use it to create a task. You create a task with an identifier, title, care plan, and schedule. You can also provide instructions for the task as shown in the second line:
+
+```swift
+var task = OCKTask(identifier: "doxylamine", title: "Take Doxylamine", carePlanID: nil, schedule: schedule)
+
+task.instructions = "Take 25mg of doxylamine when you experience nausea."
+```
+
+Next, save your task to the store. You can specify a function to handle the completion of the operation. The code below shows how to save your task, and the format of the parameters passed into the completion handler.
+
+```swift
+let storedTask = try await store.addTask(task)
+```
+
+### Handle errors
+
+If interacting with the store throws an error, you can catch the error to help troubleshoot the problem and decide how to handle it.
+
+The thrown error is an instance of `OCKStoreError`, an enumeration that contains a value and a localized description. The enumeration value is one of the following:
+
+- term `fetchFailed`: Occurs when a fetch fails.
+
+- term `addFailed`: Occurs when adding an entity fails.
+
+- term `updateFailed`: Occurs when an update to an existing entity fails.
+
+- term `deleteFailed`: Occurs when deleting an existing entity fails.
+
+- term `invalidValue`: Occurs when an invalid value is passed.
+
+- term `timedOut`: Occurs when an asynchronous action takes too long. This is intended for use by remote databases.
+
+Use this value to determine whether to retry the operation, inform the user, or handle the error some other way. To provide feedback to the user, present the localized description to the user.
+
+For example, if you attempt to add an entity to the store that’s missing required information, you receive an error enumeration with the value of `OCKStoreError.invalidValue(reason:)`, and the localized description of “OCKCDScheduleElement must have at least 1 non-zero interval.
+
+### Display Scheduled tasks
+
+Once you have a store populated with tasks, you can display those tasks to the user. CareKit provides pre-built view controllers and a range of controls and views to build your own user interface layouts.
+
+The simplest way to present data to the user is to use the pre-built view controllers. The code below builds on previous code listings, and shows how to present task data to the user using an ``OCKDailyTasksPageViewController``.
+
+```swift
+let careViewController = OCKDailyTasksPageViewController(store: store)
+self.present(careViewController, animated: true, completion: nil)
+```
+
+The ``OCKDailyTasksPageViewController``  observes changes to the store and updates the view automatically. All you need to do is instantiate it with a store and then present it.
+
+The ``OCKDailyTasksPageViewController`` displays a header, that contains a weekly calendar, and a body, that includes a list of tasks scheduled for the currently selected date. When a user selects a date in the calendar, the calendar shows all tasks scheduled for that date. When the user taps to complete a task, the controller saves it in the store.
+
+You can use view controllers and views available in CareKit to customize the user interface appearance, or use your own.

CareKit/CareKit.docc/Resources/Setting Up Your Project to Use CareKit/Setting up Your Project to Use CareKit.md

@@ -0,0 +1,49 @@
+# Setting up your project to use CareKit
+
+Add and update CareKit in your project using Swift Package Manger.
+
+## Overview
+
+CareKit is an open-source framework and is not part of Xcode. To use it, you need to add it to your project as a dependency using the Swift Package Manager in Xcode. This allows you to easily keep it up to date.
+
+You can find CareKit as a repository on GitHub: [CareKit on GitHub](https://github.com/carekit-apple/CareKit).
+
+### Add CareKit as a package dependency
+
+Add a package dependency to your Xcode project by selecting File > Swift Packages > Add Package Dependency. Next, provide the URL of the repository: https://github.com/carekit-apple/CareKit
+
+### Choose package options
+
+With the package repository specified, choose which version, branch, or commit to pull from. Unless there’s a specific commit you want to pull from, choose the stable branch. For more information on specifying versions, branches, and commits, see [Adding Package Dependencies to Your App](https://developer.apple.com/documentation/swift_packages/adding_package_dependencies_to_your_app/).
+
+### Select parts of CareKit you want to use
+
+CareKit is built to be modular, and this includes being able to use only the parts relevant to your needs. The framework includes a complete set of libraries, pre-built view controllers, the data store, and the component views. It also synchronizes data between the UI and data layers.
+
+CareKit includes CareKitUI and CareKitStore. If you only want to use the customizable views, choose CareKitUI. If you only need access to the data-persistence library, choose CareKitStore.
+
+In the ‘Choose package products and targets’ dialogue, select which part or parts you want, and the targets they should be added to:
+
+![Choose the package products](setting-up-your-project-to-use-carekit-1)
+
+### Verify the dependency
+
+To check whether the dependency was successfully included in your project, select your project in the Navigator, select the target, and under General scroll down to Frameworks, Libraries, and Embedded Content. You should see CareKit listed there:
+
+![CareKit package embedded in app](setting-up-your-project-to-use-carekit-2)
+
+If you’d like to remove CareKit from your target, select it in the list, then press the removal (-) button.
+
+Once you’ve added CareKit to your target, use it in any of your classes by importing it:
+
+```swift
+import CareKit
+```
+
+### Update CareKit
+
+Swift Package Manager makes it easy to keep your dependencies up to date. Every time you open a Xcode project that has CareKit included as a dependency, and you have an active internet connection, the Swift Package Manager checks for updates that match your specified rules for version, branch, or commit.
+
+You can also manually check for an update in Xcode by selecting File > Swift Packages > Update to Latest Package Versions:
+
+![Update Swift packages](setting-up-your-project-to-use-carekit-3)