Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-existant resources returned by Item Endpoint #12

Open
GoogleCodeExporter opened this issue Aug 3, 2015 · 1 comment
Open

Non-existant resources returned by Item Endpoint #12

GoogleCodeExporter opened this issue Aug 3, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

http://reference.data.gov.uk/doc/department/co/post/93.json

This API call returns a post with the ID "93" all fine and dandy, within my 
JavaScript I can test for the usual values such as primaryTopic._about to check 
it's been returned ok.

http://reference.data.gov.uk/doc/department/co/post/412.json

This API call uses a random (and non-existant) post ID I've typed in, yet it 
seems to still return an item, which appears to be valid - just lacking data. 

This gives the impression that this post exists within the data when I was 
hoping for something more along the lines of primaryTopic:[] (similar to 
items:[] when there are no results from a List Endpoint).

Dan

Original issue reported on code.google.com by danpaulsmith on 13 Apr 2011 at 2:34

@GoogleCodeExporter
Copy link
Author

It makes sense that item._about should signal an item exists and result._about 
should resemble the API request made.

Original comment by danpaulsmith on 13 Apr 2011 at 2:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant