tag:blogger.com,1999:blog-8988507699269858923.post3778961847889909552..comments2023-05-26T03:42:08.305-07:00Comments on Breaking Bytes: Next and Previous buttons not stopping at first/last pagebwanamarkohttp://www.blogger.com/profile/10855014295815183523noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8988507699269858923.post-34031368336078994442012-02-24T00:24:11.682-08:002012-02-24T00:24:11.682-08:00So I believe that issue is that the method JSONObj...So I believe that issue is that the method JSONObject.getString() is coercing the sentinel JSONObject.NULL to String "null" but that doesn't explain why I thought it was working before. Obviously at some point I should try an older commit and see if it did really work or not, and why.bwanamarkohttps://www.blogger.com/profile/10855014295815183523noreply@blogger.comtag:blogger.com,1999:blog-8988507699269858923.post-47779732666559244402012-02-14T09:28:14.921-08:002012-02-14T09:28:14.921-08:00No, it turns out it was not a change in the Sifter...No, it turns out it was <b><i>not</i></b> a change in the SifterAPI, see <a href="http://groups.google.com/group/sifterapi/browse_thread/thread/5d92e6723c67b15a" rel="nofollow">this post</a> on SifterAPI Google Groups Support.bwanamarkohttps://www.blogger.com/profile/10855014295815183523noreply@blogger.comtag:blogger.com,1999:blog-8988507699269858923.post-26828765563440757642012-02-14T02:25:17.143-08:002012-02-14T02:25:17.143-08:00This bug has been resolved. See issue #25 for more...This bug has been resolved. See <a href="https://bitbucket.org/bwanamarko/sifterreader/issue/25/next-and-previous-buttons-not-stopping-at" rel="nofollow">issue #25</a> for more details. Basically, I think there was a change in the SifterAPI. In the Issues Listing there are two fields for the previous and next page url, but if you're at the first or last page then it should say null. It used to use the primitive null, but somehow it got switched to a String.bwanamarkohttps://www.blogger.com/profile/10855014295815183523noreply@blogger.com