-
Notifications
You must be signed in to change notification settings - Fork 201
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
what are 'errors' and 'includes' properties in the getEntries() response object? #69
Comments
Hi @chriswu14, these are properties returned by the Contentful REST API. The As for the |
Thanks for the reply, I figured later on that I started my account with a prefilled sample one and deleted some of the author content may be there was some linking between them. |
@trodrigues Hey, I know this is an old issue but theres still some inconsistencies, at least from my understanding, with the Its described here as the place where linked asset/entry data is resolved (i.e. urls). The language is very vague, for instance:
And from here
What the hell is "when not already fetched in the items array" or "if the standard items array has not already...."?. If Im writing an app, I need to know exactly where in the response Im getting my data. Is it gonna be in Basically - How will I know, programmatically, when the linked entities will be in the |
Hi @HauntedSmores, Best, |
@Khaledgarbaya Thanks a lot for the clarification. I also had the same explanation from contentful support, who are always on the ball. Great work on the SDK and the platform in general. My team let me run with Contentful for my current project and I think I may have successfully killed WordPress around here. Thanks for that! |
this is what my client code look like, everything works fine I get my content but when I am learning based on the API documentation I cannot find any info about these two objects.
var client = contentful.createClient({ accessToken: '****', space: '****' }); client.getEntries().then(entries => { console.log(entries) })
the response is
The text was updated successfully, but these errors were encountered: