Merge all ObjC Frameworks #1230
Conversation
flovilmart
force-pushed
the
refactor-structure
branch
from
7f5c89a to
3dfc01f
Compare
montymxb
left a comment
montymxb
left a comment
There was a problem hiding this comment.
This just for reviewing the README. Trusting everything else (827 files changed 😱 ). Just a typo and a question.
README.md
Outdated
| pod 'Parse/UI | ||
| ``` | ||
|
|
||
| Note that in this case, the Parse framework will contain all header, so you just have to use: |
| @@ -107,12 +135,9 @@ of patent rights can be found in the PATENTS file in the same directory. | |||
| As of April 5, 2017, Parse, LLC has transferred this code to the parse-community organization, and will no longer be contributing to or distributing this code. | |||
|
|
|||
| [docs]: http://docs.parseplatform.org/ios/guide/ | |||
| [blog]: http://blog.parse.com/ | |||
There was a problem hiding this comment.
I removed it as it may not contain any relevant information anymore about this repo. This seemed to be an artifact of the old parse.com where some articles would be pushed out about new SDK features or demo usages.
There was a problem hiding this comment.
That's fine then. I want to get back to a point where we consistently put up posts about what we're doing, like coalescing all the ObjC frameworks 😉 .
There was a problem hiding this comment.
yeah, I'll write something this week, when deprecating / archiving the other repos.
|
@montymxb I copy pasted the code from the other repos. |
|
and addressed the nits ;) |
montymxb
left a comment
montymxb
left a comment
There was a problem hiding this comment.
Genehmigt 
. Assuming other code is good as it is unchanged from it's prior locations.
This PR integrates the FacebookUtils and TwitterUtils repo into a single codebase.
We'll probably need to re-work further the readme.
The motivation is to keep a single codebase for those libraries, and be able to distribute them all at once, instead of managing a lot of boilerplate ci code.
It also uses circle CI for the build status, and travis for releases deployment (easier to push to github for now etc...)
What's to be reviewed? Probably just the README