[twitter-dev] String IDs in keyless JSON arrays

2010-11-17 Thread Tim
I noticed a short while ago that keyless array responses, e.g.
[182097517,183706717,...]
were switched to string IDs, e.g. [182097517,183706717,...]
Example method blocks/ids

This appears to have reverted to integer IDs.

I switched my code to take advantage of the change, and I have to
switch back to fix my app.

What's the official word on this, please?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] String IDs in keyless JSON arrays

2010-11-17 Thread Thomas Mango

The last mention of this I saw was here:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/92ff8f4b9eae5293/4d298d877ec5de3b

I haven't used it, but the stringify_ids parameter looks like it will 
(already does?) convert the response to an array of strings.


Tim wrote:

I noticed a short while ago that keyless array responses, e.g.
[182097517,183706717,...]
were switched to string IDs, e.g. [182097517,183706717,...]
Example method blocks/ids

This appears to have reverted to integer IDs.

I switched my code to take advantage of the change, and I have to
switch back to fix my app.

What's the official word on this, please?




--
Thomas Mango
tsma...@gmail.com


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk