Closed eladb closed 10 years ago
Thank you @eladb! Unfortunately (or fortunately, depending on who you ask :), we are no longer using Parse at our startup. Would you like to take ownership of this repo?
Sure, why not
On Thu, Jun 5, 2014 at 2:00 PM, martinrybak notifications@github.com wrote:
Thank you @eladb https://github.com/eladb! Unfortunately (or fortunately, depending on who you ask :), we are no longer using Parse at our startup. Would you like to take ownership of this repo?
— Reply to this email directly or view it on GitHub https://github.com/updatezen/Parse-NSCoding/pull/11#issuecomment-45206046 .
How do you want to handover the project? (cocoa pods assignment + github)
I just transferred the Github repo to you. Not sure what you mean about cocoapods assignment. The old repo URL will be redirected to your new repo URL.
I would need a way to publish the pod. I think that should do the trick:
pod trunk add-owner Parse-NSCoding elad.benisrael@gmail.com
On Thu, Jun 5, 2014 at 7:05 PM, martinrybak notifications@github.com wrote:
I just transferred the Github account to you. Not sure what you mean about cocoapods assignment. The old repo URL will be redirected to your new repo URL.
— Reply to this email directly or view it on GitHub https://github.com/martinrybak/Parse-NSCoding/pull/11#issuecomment-45239165 .
I haven't claimed ownership yet, so go ahead
CoolE.
On Fri, Jun 6, 2014 at 2:41 AM, martinrybak notifications@github.com wrote:
I haven't claimed ownership yet, so go ahead
Reply to this email directly or view it on GitHub: https://github.com/eladb/Parse-NSCoding/pull/11#issuecomment-45288581
Perhaps a better way to validate properties that can be encoded: https://github.com/chaitanyapandit/Parse-NSCoding/commit/b359c20c2dbc198488e5f51db15f9061ed06b053
Parse added a few ivars that cannot be archived which broke the category. Instead, store the URL of the file explicitly.