Letractively / dotnetkicks

Automatically exported from code.google.com/p/dotnetkicks
1 stars 0 forks source link

getUpcomingStories returns another view than upcoming on web site #125

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Download the JSON data returned by getUpcomingStories:
http://www.dotnetkicks.com/services/json/jsonservices.ashx/getUpcomingStori
es 

What is the expected output? 
Expected the same view as (sorted by creation time?):
http://www.dotnetkicks.com/upcoming

What do you see instead?
Stories are sorted by kicks in descending order (popular upcoming 
stories?). Is this intended?

Original issue reported on code.google.com by azizatif on 28 Sep 2007 at 10:03

GoogleCodeExporter commented 9 years ago
Thanks, I'll refactor these services into the models so that the Web.UI and any 
APIs
use the same code.

Original comment by gavinjo...@gmail.com on 28 Sep 2007 at 10:49

GoogleCodeExporter commented 9 years ago
I have refactored the API and there also are three new API operations:

 - getFrontPageStoriesPaged(pageNumber, pageSize)
 - getUpcomingPageStories()
 - getUpcomingPageStoriesPaged(pageNumber, pageSize)

API BREAKING CHANGE:

All operations that return a page of data now return the generic type
ApiPagedList<T>. The get stories operations now return ApiPagedList<ApiStory>. 
This
means that all existing client application will break. The story collection 
used to be:

  result.stories

it used to be:

  result.items

Original comment by gavinjo...@gmail.com on 28 Sep 2007 at 1:33

GoogleCodeExporter commented 9 years ago
Thanks, Gavin. I just got home and realized that the live kicks client I built 
wasn't displaying stories anymore and I guess this explains it. I'll adjust it 
according to the new changes.

Original comment by azizatif on 28 Sep 2007 at 7:33