Re: Will this break your app? Chime in!
That's reasonable. Happy to delay it. On Wed, Dec 17, 2008 at 11:38, Hayes Davis wrote: > This will break my app. Personally I'd like to see it wait until after the > holidays as I think everyone that's used this method has worked around its > return value. The day after Christmas isn't a great time to be dealing with > API changes. > Glad to see the change though. I'm looking forward to getting rid of the > special case. > > Hayes > > On Tue, Dec 16, 2008 at 11:48 PM, Alex Payne wrote: >> >> At this point, I'm planning on a deploy on Friday, Dec 26. Happy to >> delay it if need be. >> >> On Tue, Dec 16, 2008 at 19:31, Colby Palmer wrote: >> > >> > I added a fix to handle both responses, so I'm good. I'll just look >> > out for your note that this fix is deployed and remove the old string >> > response. Thanks for the heads up! >> > >> >> >> >> -- >> Alex Payne - API Lead, Twitter, Inc. >> http://twitter.com/al3x > > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Will this break your app? Chime in!
This will break my app. Personally I'd like to see it wait until after the holidays as I think everyone that's used this method has worked around its return value. The day after Christmas isn't a great time to be dealing with API changes. Glad to see the change though. I'm looking forward to getting rid of the special case. Hayes On Tue, Dec 16, 2008 at 11:48 PM, Alex Payne wrote: > > At this point, I'm planning on a deploy on Friday, Dec 26. Happy to > delay it if need be. > > On Tue, Dec 16, 2008 at 19:31, Colby Palmer wrote: > > > > I added a fix to handle both responses, so I'm good. I'll just look > > out for your note that this fix is deployed and remove the old string > > response. Thanks for the heads up! > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x >
Re: Will this break your app? Chime in!
At this point, I'm planning on a deploy on Friday, Dec 26. Happy to delay it if need be. On Tue, Dec 16, 2008 at 19:31, Colby Palmer wrote: > > I added a fix to handle both responses, so I'm good. I'll just look > out for your note that this fix is deployed and remove the old string > response. Thanks for the heads up! > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Will this break your app? Chime in!
I added a fix to handle both responses, so I'm good. I'll just look out for your note that this fix is deployed and remove the old string response. Thanks for the heads up!
Re: Will this break your app? Chime in!
Thanks :) Also, please consider to fix issue #157. If you do, I can use show method only to get friends existence then I can reduce 1 API call. http://code.google.com/p/twitter-api/issues/detail?id=157 Thanks, Kazuho On Tue, Dec 16, 2008 at 5:09 PM, Alex Payne wrote: > > Example response: > > true > > That's it :) Just a bare boolean literal. > > On Tue, Dec 16, 2008 at 17:06, Kazuho Okui wrote: >> >> This will break my app. 1 week to 10 days to get an approval from Apple. >> >> Also, please give us a example of new response. >> >> On Tue, Dec 16, 2008 at 4:53 PM, Cameron Kaiser wrote: >>> As per http://code.google.com/p/twitter-api/issues/detail?id=202, I'd like to return a proper boolean in the JSON response for /friendships/exists. Will this break your app? If so, how much time to do you need to ship a fix? >>> >>> TTYtter uses its own internal JSON parser and in fact special cases trivial >>> Booleans and stringified Booleans: >>> >>>if ($data =~ /^['"]?(true|false)['"]?$/); >>> >>> So it will accept any of "true", true, "false", false, etc. If you decided >>> to wrap it in something, though, I'd need to account for that. As described >>> in the issue, it should be okay. >>> >>> -- >>> personal: >>> http://www.cameronkaiser.com/ -- >>> Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com >>> -- He whose face gives no light, shall never become a star. -- William >>> Blake -- >>> >> > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x >
Re: Will this break your app? Chime in!
Example response: true That's it :) Just a bare boolean literal. On Tue, Dec 16, 2008 at 17:06, Kazuho Okui wrote: > > This will break my app. 1 week to 10 days to get an approval from Apple. > > Also, please give us a example of new response. > > On Tue, Dec 16, 2008 at 4:53 PM, Cameron Kaiser wrote: >> >>> As per http://code.google.com/p/twitter-api/issues/detail?id=202, I'd >>> like to return a proper boolean in the JSON response for >>> /friendships/exists. Will this break your app? If so, how much time >>> to do you need to ship a fix? >> >> TTYtter uses its own internal JSON parser and in fact special cases trivial >> Booleans and stringified Booleans: >> >>if ($data =~ /^['"]?(true|false)['"]?$/); >> >> So it will accept any of "true", true, "false", false, etc. If you decided >> to wrap it in something, though, I'd need to account for that. As described >> in the issue, it should be okay. >> >> -- >> personal: http://www.cameronkaiser.com/ >> -- >> Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com >> -- He whose face gives no light, shall never become a star. -- William Blake >> -- >> > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Will this break your app? Chime in!
This will break my app. 1 week to 10 days to get an approval from Apple. Also, please give us a example of new response. On Tue, Dec 16, 2008 at 4:53 PM, Cameron Kaiser wrote: > >> As per http://code.google.com/p/twitter-api/issues/detail?id=202, I'd >> like to return a proper boolean in the JSON response for >> /friendships/exists. Will this break your app? If so, how much time >> to do you need to ship a fix? > > TTYtter uses its own internal JSON parser and in fact special cases trivial > Booleans and stringified Booleans: > >if ($data =~ /^['"]?(true|false)['"]?$/); > > So it will accept any of "true", true, "false", false, etc. If you decided > to wrap it in something, though, I'd need to account for that. As described > in the issue, it should be okay. > > -- > personal: http://www.cameronkaiser.com/ > -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com > -- He whose face gives no light, shall never become a star. -- William Blake > -- >
Re: Will this break your app? Chime in!
> As per http://code.google.com/p/twitter-api/issues/detail?id=202, I'd > like to return a proper boolean in the JSON response for > /friendships/exists. Will this break your app? If so, how much time > to do you need to ship a fix? TTYtter uses its own internal JSON parser and in fact special cases trivial Booleans and stringified Booleans: if ($data =~ /^['"]?(true|false)['"]?$/); So it will accept any of "true", true, "false", false, etc. If you decided to wrap it in something, though, I'd need to account for that. As described in the issue, it should be okay. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- He whose face gives no light, shall never become a star. -- William Blake --
Will this break your app? Chime in!
As per http://code.google.com/p/twitter-api/issues/detail?id=202, I'd like to return a proper boolean in the JSON response for /friendships/exists. Will this break your app? If so, how much time to do you need to ship a fix? We won't schedule a deploy for this fix until we've heard back from you. Thanks in advance for letting us know. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
