Skip to content

Commit 96e9685

Browse files
authored
Update packages (#19)
1 parent 848e65d commit 96e9685

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

Package.resolved

Lines changed: 6 additions & 6 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Package.swift

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ let package = Package(
1414
.library(name: "ParseServerSwift", targets: ["ParseServerSwift"])
1515
],
1616
dependencies: [
17-
.package(url: "https://github.com/vapor/vapor.git", .upToNextMajor(from: "4.74.0")),
17+
.package(url: "https://github.com/vapor/vapor.git", .upToNextMajor(from: "4.74.1")),
1818
.package(url: "https://github.com/netreconlab/Parse-Swift.git",
19-
.upToNextMajor(from: "5.1.0")),
19+
.upToNextMajor(from: "5.3.0")),
2020
],
2121
targets: [
2222
.target(

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ To start your server type, `swift run` in the terminal of the project root direc
124124

125125
## Writing Cloud Code
126126
### Creating `ParseObject`'s
127-
It is recommended to add all of your `ParseObject`'s in a folder called `Models` similar to [ParseServerSwift/Sources/ParseServerSwift/Models](https://github.com/netreconlab/ParseServerSwift/blob/main/Sources/ParseServerSwift/Models).
127+
It is recommended to add all of your `ParseObject`'s in a folder called `Models` similar to [ParseServerSwift/Sources/ParseServerSwift/Models](https://github.com/netreconlab/ParseServerSwift/blob/main/Sources/ParseServerSwift/Models). Note that in the [Apple's WWDC User Xcode for server-side development](https://developer.apple.com/videos/play/wwdc2022/110360/), it is recommended to create packages (15:26 mark) to house your models to share between server and clients apps and reduce code repition.
128128

129129
#### The `ParseUser` Model
130130
Be mindful that the `ParseUser` in `ParseServerSwift` should conform to [ParseCloudUser](https://swiftpackageindex.com/netreconlab/parse-swift/4.16.2/documentation/parseswift/parseclouduser). This is because the `ParseCloudUser` contains some additional properties on the server-side. On the client, you should always use `ParseUser` instead of `ParseCloudUser`. In addition, make sure to add all of the additional properties you have in your `_User` class to the `User` model. An example `User` model is below:

0 commit comments

Comments
 (0)