-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix version 3.0 beta build #691
Changes from 54 commits
8f92969
b33f1de
5f0cf46
0a313d0
a92cb94
f07bfef
7cd56b1
30a86e1
dde967d
8bc33a7
83d81e4
f672696
741b0f2
2f7b8d4
3f5e441
92a6c02
b5952ab
3ed479a
2fda297
1a66556
5d2500b
38be8ce
4bf2d81
863a5e8
9434c08
35b78d5
e99114c
cee8e25
2b7741e
c37c9a4
c0b3dd1
47482b7
032abb2
e7e9ffa
32c6bf0
644424b
f8d0a81
38b9ef8
27f525c
3a43129
ff6ccbe
78f4bec
2712c6e
05e292a
50b4d9f
6d65a07
a742f62
e426d56
ada41bb
ef51eff
708d0ec
636aaae
7839f08
38c496d
951d081
5d10809
fdfcbf3
225341b
698176a
b67404d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
version: 1 | ||
builder: | ||
configs: | ||
- documentation_targets: ["CareKit", "CareKitUI", "CareKitStore", "CareKitFHIR"] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interesting, where do the built docs end up? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. SPI hosts them on their website, though you can keep building the docs on GitHub pages. You can see the ones I made for ParseCareKit (the version that works with the latest main of CareKit 2.x): https://swiftpackageindex.com/netreconlab/ParseCareKit/0.13.1/documentation/parsecarekit Here's the Alpha to the version of ParseCareKit that works with CareKit 3.0.0 beta: https://swiftpackageindex.com/netreconlab/ParseCareKit/1.0.0-alpha.7/documentation/parsecarekit The breadcrumbs on the site only show the latest, but all old versions remain hosted so devs can always view the docs for the version they are using. Here's an older version of my docs: https://swiftpackageindex.com/netreconlab/ParseCareKit/0.13.0/documentation/parsecarekit There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You don't have to do anything special to release these other than having the Note: I haven't had a multi-framework project, so I'm assuming I set this up correctly based on the SPI docs. I also ran the SPI verification and it passed. We can ask @finestructure if I setup this line correctly for documentations for multiple frameworks. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi Corey 👋 , yes, that's correct! The order determines the order in the drop-down menu and the first one is the one we show by default. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Awesome Sven, thanks for looking at this! |
||
platform: ios | ||
- platform: ios | ||
scheme: "CareKit" | ||
- platform: watchos | ||
scheme: "CareKit" | ||
Comment on lines
+5
to
+9
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It looks like SPI automatically infers a configuration based on our repo, can you walk me through why this file is explicitly needed? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It can most of the time, but sometimes it can’t. The latest changes you pushed combined the targets, but it’s possible SPI can still make a mistake because there are multiple frameworks in one. You can see the builds for CareKit here: https://swiftpackageindex.com/carekit-apple/CareKit/builds For the build profile, SPI only builds 1 framework (I believe) which is the one specified here. Also, the docs won’t build without being told specifically to do so in the spi file There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let me know if need me to answer more questions from the comment added here: https://github.com/carekit-apple/CareKit/pull/691/files#r1162276983 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. add macOS |
cbaker6 marked this conversation as resolved.
Show resolved
Hide resolved
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this bit needed? Is CareKitUI not running on watchOS 9.1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was just all of the tests in the framework are for iOS, there are no current watchOS tests so I skipped it, it builds fine though
If we remove these lines, it will add ~5 minutes to the CI, but will automatically test CareKitUI for watchOS when tests are added in the future. I can remove the exclude if you want me to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add this back