![]() ![]() where: This argument allows you to filter the query responses from the list of entries present in the content type.Let’s look at the different arguments we can use in the query: Any files of type image will have the following schema: Let’s understand the schema generated for some of the commonly referred system-defined fields.Ĭontentstack has a pre-defined asset object class. Here’s a list of system-defined fields generated by Contentstack’s GraphQL Content Delivery API: This helps detect and avoid the use of any reserved GraphQL typenames or user-defined fields. Tip: You can use an API client, such as GraphiQL Explorer, to run queries and explore Contentstack's GraphQL Content Delivery API before writing your application code. Their GraphQL type names are reserved and any user-defined fields that result in the same type will return the SCHEMA_BUILD_ERROR error message. Using it, you can skip the content type(s) causing the schema build error and view the rest of your stack data.Ĭertain fields in Contentstack are predefined. This parameter comes really handy when you encounter a SCHEMA_BUILD_ERROR during introspection queries. You need to pass an array of content type UIDs to this parameter. To skip certain content types when retrieving content, you can make use of the skip_content_type_uids= query parameter. Note: The 'SysAsset' GraphQL type will not be available in the paginated Introspection queries. By default, the content types in the schema are sorted based on title_ASC and cannot be modified. ![]() ![]() You can also paginate the response schema returned by the Introspection system by passing the skip and limit parameters in the query. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |