|
1 | 1 | # JSONAPI |
2 | | -[](http://opensource.org/licenses/MIT) [](https://swift.org) [](https://github.com/mattpolzin/JSONAPI/actions/workflows/tests.yml) |
| 2 | +[](http://opensource.org/licenses/MIT) [](https://swift.org) [](https://github.com/mattpolzin/JSONAPI/actions/workflows/tests.yml) |
3 | 3 |
|
4 | 4 | A Swift package for encoding to- and decoding from **JSON API** compliant requests and responses. |
5 | 5 |
|
@@ -58,35 +58,15 @@ If you find something wrong with this library and it isn't already mentioned und |
58 | 58 |
|
59 | 59 | ## Dev Environment |
60 | 60 | ### Prerequisites |
61 | | -1. Swift 5.2+ |
62 | | -2. Swift Package Manager, Xcode 11+, or Cocoapods |
| 61 | +1. Swift 6.0+ |
| 62 | +2. Swift Package Manager |
63 | 63 |
|
64 | 64 | ### Swift Package Manager |
65 | 65 | Just include the following in your package's dependencies and add `JSONAPI` to the dependencies for any of your targets. |
66 | 66 | ```swift |
67 | | -.package(url: "https://github.com/mattpolzin/JSONAPI.git", from: "5.1.0") |
| 67 | +.package(url: "https://github.com/mattpolzin/JSONAPI.git", from: "6.0.0") |
68 | 68 | ``` |
69 | 69 |
|
70 | | -### Xcode project |
71 | | -With Xcode 11+, you can open the folder containing this repository. There is no need for an Xcode project, but you can generate one with `swift package generate-xcodeproj`. |
72 | | - |
73 | | -### CocoaPods |
74 | | -To use this framework in your project via Cocoapods, add the following dependencies to your Podfile. |
75 | | -```ruby |
76 | | -pod 'Poly', :git => 'https://github.com/mattpolzin/Poly.git' |
77 | | -pod 'MP-JSONAPI', :git => 'https://github.com/mattpolzin/JSONAPI.git' |
78 | | -``` |
79 | | - |
80 | | -### Carthage |
81 | | -This library does not support the Carthage package manager. This is intentional to avoid an additional dependency on Xcode and the Xcode's project files as their format changes throughout versions (in addition to the complexity of maintaining different shared schemes for each supported operating system). |
82 | | - |
83 | | -The difference between supporting and not supporting Carthage is the difference between maintaining an Xcode project with at least one shared build scheme; I encourage those that need Carthage support to fork this repository and add support to their fork by committing an Xcode project (you can generate one as described in the [Xcode project](#xcode-project) section above). Once an Xcode project is generated, you need to mark at least one scheme as [shared](https://github.com/Carthage/Carthage#share-your-xcode-schemes). |
84 | | - |
85 | | -### Running the Playground |
86 | | -To run the included Playground files, create an Xcode project using Swift Package Manager, then create an Xcode Workspace in the root of the repository and add both the generated Xcode project and the playground to the Workspace. |
87 | | - |
88 | | -Note that Playground support for importing non-system Frameworks is still a bit touchy as of Swift 4.2. Sometimes building, cleaning and building, or commenting out and then uncommenting import statements (especially in the` Entities.swift` Playground Source file) can get things working for me when I am getting an error about `JSONAPI` not being found. |
89 | | - |
90 | 70 | ## Deeper Dive |
91 | 71 | - [Project Status](./documentation/project-status.md) |
92 | 72 | - [Server & Client Example](./documentation/examples/client-server-example.md) |
|
0 commit comments