-
Notifications
You must be signed in to change notification settings - Fork 756
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
Add iOS framework target #36
Conversation
Codecov Report
@@ Coverage Diff @@
## master #36 +/- ##
==========================================
- Coverage 76.05% 74.51% -1.55%
==========================================
Files 39 33 -6
Lines 2360 1891 -469
Branches 123 100 -23
==========================================
- Hits 1795 1409 -386
+ Misses 508 437 -71
+ Partials 57 45 -12
Continue to review full report at Codecov.
|
This closes #25. Also not sure if you guys need an example in the repo |
@hzalaz @WilliamDenniss Any updates on the review above? Carthage support is a must for growth in the iOS community. |
Reviewed 1 of 6 files at r1. Source/Framework/AppAuth.h, line 1 at r1 (raw file):
I feel we should be using the same umbrella header that already exists, otherwise we will have to keep multiple umbrella headers in sync? Comments from Reviewable |
Review status: 1 of 6 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. Source/Framework/AppAuth.h, line 1 at r1 (raw file): Previously, StevenEWright (Steven E Wright) wrote…
Yes, it's not ideal but I think the framework umbrella header should use the Comments from Reviewable |
Review status: 1 of 6 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. Source/Framework/AppAuth.h, line 1 at r1 (raw file): Previously, hzalaz (Hernan Zalazar) wrote…
Ah, yes, I see, and you are right. I didn't realize the existing umbrella header wasn't referencing the files that way. Let me chat with William and see what's up. Do you have a suggestion in the meantime? Comments from Reviewable |
@WilliamDenniss PTAL |
Did this request die, or are someone still working on it? Not having Carthage support is really annoying when we were finally about to replace cocoa pods with something a lot better. |
I'd love to see Carthage support. This PR needs to be updated with new classes that were added, and I'd like to see an example project in If someone can do that work to refresh the PR, I'll make sure this gets reviewed ASAP. |
@WilliamDenniss will take care of that |
@WilliamDenniss updated the PR with latest master changes and also added targets for tvOS & macOS fwk besides iOS. Also added a new example project using Carthage, it's configured to pull the dependency from this repo for when its merged but if you need to test you need to change the Cartfile to use my fork Is there any way I can see why the build failed? |
iOS framework target that allows lib to be included using Carthage.
This change is