Apollo documentation

Apollo documentation DEFAULT


This is an entirely configuration-based Gatsby theme that generates a documentation website based on a series of Markdown or MDX files. It also exports a series of components that can be used within MDX files.


If you’re using this package, you’ll also need to install and its peer dependencies, and . Next, install the theme:


You can configure for use with any set of docs using the provided configuration options. You may also use component shadowing to customize elements like the logo or color scheme.


Option nameTypeRequiredDescription
rootstringYesMust be
siteNamestringYesThe main title for the website, used in the element and top left corner of the site
descriptionstringYesThe site description for SEO and social (FB, Twitter) tags
sidebarCategoriesobjectYesAn object mapping categories to page paths (see reference)
subtitlestringNoThe page title that gets rendered above the sidebar navigation
pageTitlestringNoThe string to be rendered in the page’s tag. If omitted, will be used.
baseDirstringNoIf your Gatsby site does not live in the root of your project directory/git repo, pass the subdirectory name here (, for example)
contentDirstringNoThe directory where docs content exists ( by default)
githubHoststringNoThe hostname of the GitHub server ( by default)
githubRepostringNoThe owner and name of the content repository on GitHub
spectrumPathstringNoThe path to be appended to Spectrum links
gaTrackingIdstringNoYour site’s Google Analytics tracking ID
algoliaApiKeystringNoYour Algolia DocSearch API key
algoliaIndexNamestringNoThe name of your DocSearch index
shareImageConfigstringNoThe configuration object for Cloudinary social cards see docs for options
baseUrlstringNoThe origin where your website will be hosted (e.g. )
spectrumHandlestringNoYour Spectrum community’s handle/slug
twitterHandlestringNoYour Twitter handle, without the ”@”
youtubeUrlstringNoThe URL of your YouTube channel
defaultVersionstringNoAn identifier for the default selected version, served at the root of the docset (/)
localVersionstringNoIf the local files represent a version different from the , specify an identifier for the local version here
versionsarrayNoAn array of objects representing the versions that the website should generate
navConfigobjectNoAn object defining the top-left navigation links (see reference)
checkLinksOptionsobjectNoOptions accepted by
ignorearrayNoFiles to ignore using anymatch-compatible definition pattern
gatsbyRemarkPluginsarrayNoAdditional Gatsby Remark plugins to pass to and
remarkPluginsarrayNoAdditional Remark plugins to pass to

If omitted, only one version of docs will be built, based on the files in the theme consumer repository. If provided, the option expects an object mapping older versions’ labels to their respective git branch. The current filesystem will still determine the “default” version. The default label for this version is “Latest”, but is configurable by the option.

The option is an object keyed by category titles. Each entry in the object is an array of page paths. The path should resemble the location of a Markdown/MDX file in the git repository, relative to , and without the .md extension. Sidebar navigation items that are not a member of a category live under the key. To add an external link to your sidebar, your can provide a string formatted like a Markdown link.

The option should be an object keyed by link titles. The values should be objects with , and properties. Check out the default theme options for an example of the expected shape of this data.

Algolia configuration

This theme allows you to use Algolia DocSearch to power a search bar in the site. You’ll need to provide your API key and index name to the theme in the form of and options.

To get these, sign up with DocSearch for an open source repo. You’ll be able to configure your indexing strategy by submitting a PR to edit your config file in the repo.

Creating pages

This theme generates pages based on Markdown or MDX files in the directory of a repo. Your Markdown/MDX files should contain some frontmatter defining their titles and descriptions.

Page URLs will be derived from the file paths of your Markdown. You can nest Markdown files within directories to create pages with additional path segments. You can overwrite this default path by adding a field to your Markdown frontmatter header.

Component shadowing

You can customize a website using this theme further by taking advantage of component shadowing.

By default, this theme sets the website favicon to the one from Apollo’s website within its internal component. If you wanted to use your own favicon, you could shadow the component within your site and add your custom SEO/favicon implementation.


This theme exports React components that you can use in MDX files throughout a documentation website.

An expandable panel of content used to hide complex information or instructions that might be a tangent from the main topic of the content it lives within.

childrennodeThe content of the panel, usually includes an
titlestringThe title of the panel, visible even when the panel is closed

A wrapper element that should be used in conjunction with components. It renders an element with some styles baked in.

A list item for use with the . It comes with a cicular area to its left to render a number, glyph, or some way to indicate progress through a set of instructions. You can write Markdown within these elements if you keep everything detabbed and add an empty line between your content and the component’s opening and closing tags.

childrennodeThe content of the list item, usually a block of Markdown
numberstringThe number displayed to the left of the list item, or a checkmark if “check” is passed

Wraps adjacent code blocks to allow users to toggle between them using a dropdown menu.


All docs sites will eventually be deployed into a subdirectory, as configured by the option—/docs/apollo-server, for example. Read this guide to learn more about publishing to a subdirectory.


To migrate an older Hexo site to this theme, follow this guide.


Are you using this theme in your own project? Submit a PR with your website added to this list!



Sours: https://www.gatsbyjs.com/plugins/gatsby-theme-apollo-docs/

Welcome! 👋 Apollo is a platform for building a data graph, a communication layer that seamlessly connects your application clients (such as React and iOS apps) to your back-end services.

Apollo Basics

Learn about each part of the Apollo platform and how they all work together.

Apollo Server

Configure a production-ready GraphQL server to fetch and combine data from multiple sources.

Apollo Client (React)

Manage the entirety of your React app's state and seamlessly execute GraphQL operations.

Apollo Graph Manager

Integrate with Apollo's cloud service for schema versioning, metrics, and enhanced security.

Apollo Client (iOS)

Manage the entirety of your iOS app's state and seamlessly execute GraphQL operations.

Apollo Link

Define a custom chain of actions that your client performs with each GraphQL operation.

New to Apollo or GraphQL?

It's easy to adopt Apollo incrementally, meaning you can set it up alongside an existing solution (such as a REST API) and migrate functionality at your convenience.

Edit on GitHub

Sours: https://apollographql-jp.com/
  1. Linkedin learning git
  2. Sophia mena
  3. Simmental sale reports
  4. Best warzone drops
  5. Ford thunderbird specs

Privacy Preference Center

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information

Manage Consent Preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.

Sours: https://www.apollographql.com/docs
Understanding Caching in Apollo Client 3 by Laura Beatris.


Write queries, not code#

Apollo Angular is the ultra-flexible, community driven GraphQL client for Angular, JavaScript, and native platforms. It is designed from the ground up to make it easy to build UI components that fetch data with GraphQL. To get the most value out of Apollo Client, you should use it with one of its view layer integrations. To get started with the Angular integration, go to Get Started.

  1. Incrementally adoptable, so that you can drop it into an existing JavaScript app and start using GraphQL for just part of your UI.
  2. Universally compatible, so that Apollo works with any build setup, any GraphQL server, and any GraphQL schema.
  3. Simple to get started with, so you can start loading data right away and learn about advanced features later.
  4. Inspectable and understandable, so that you can have great developer tools to understand exactly what is happening in your app.
  5. Built for interactive apps, so your users can make changes and see them reflected in the UI immediately.
  6. Small and flexible, so you don't get stuff you don't need. The core is under 12kb compressed.
  7. Community driven, because Apollo is driven by the community and serves a variety of use cases. Everything is planned and developed in the open.

These docs will help you to go from getting started with Apollo to becoming an expert!

Getting Started#

The docs are divided into three distinct sections to make it easy to find your way around:

  1. Basics, which outline the why and how of using Apollo Angular to build your application.
  2. Features, which showcase some of the advanced capabilities of Apollo Angular that your app may need.
  3. Recipes, to isolate and explain how to do common patterns.

Getting started is as simple as installing a few libraries from npm! The Get Started is a good place to start your adventure with Apollo!

Compatible tools#

We want you to love working with Apollo Angular, so we work extra hard to make sure it works with the client or server tools you're already using! The maintainers and contributors focus on solving the hard problems around GraphQL caching, request management, and UI updating, and we want that to be available to anyone regardless of their technical requirements and preferences for other parts of the app.

The Angular toolbox#

Apollo is lovingly designed to work nicely with all of the tools used by today's Angular developers. Here are some in particular:

  • Angular Schematics: Apollo Angular supports and
  • NativeScript: Apollo works out of the box in NativeScript.
  • Angular Router: Apollo Client is completely router-independent, which means you can use it with any version of Angular Router or any other routing library for Angular. It's even easy to set up server-side rendering.
  • Ionic: Apollo works great with Ionic Framework apps written in Angular

If you have a favorite Angular tool, and something in Apollo makes it difficult to integrate, please open an issue and let's work together to make it work nicely and add it to the list!

GraphQL servers#

We believe that using GraphQL should be easy and fun. One of the ways Apollo is designed for this is that if you can write your query in GraphiQL, it'll work with Apollo Client! Because it doesn't assume anything beyond the official GraphQL specification, Apollo works with every GraphQL server implementation, for every language. It doesn't impose any requirements on your schema either! If you can send a query to a standard GraphQL server, Apollo can handle it. You can find a list of GraphQL server implementations on graphql.org.

Other JavaScript + native platforms#

This documentation site is written with examples using Angular, but Apollo has an implementation for every client platform:

Sours: https://apollo-angular.com/docs/

Documentation apollo

The API section is a complete reference of every single feature available in React Apollo. If you are just getting started with React Apollo then you should read “usage” articles starting at Queries first, and come back to this API reference when you need to look up a particular method.


These APIs are not React-specific, but every React developer using Apollo needs to be aware of them.


import { gql } from'react-apollo';

The template tag is what you use to define GraphQL queries in your Apollo Client apps. It parses your GraphQL query into the GraphQL.js AST format which may then be consumed by Apollo Client methods. Whenever Apollo Client is asking for a GraphQL query you will always want to wrap it in a template tag.

You can embed a GraphQL document containing only fragments inside of another GraphQL document using template string interpolation. This allows you to use fragments defined in one part of your codebase inside of a query define in a completely different file. See the example below for a demonstration of how this works.

For convenience the tag is re-exported in from the package.


Notice how in the variable we not only include the variable through template string interpolation (), but we also include a spread for the fragment in our query.























const fragments = gql`

fragment foo on Foo {






fragment bar on Bar {






const query = gql`

query {






import { ApolloClient } from'react-apollo';

An instance is the core of the API for Apollo. It contains all of the methods you would need to interact with your GraphQL data, and it is the class you will use no matter which integration you are using.

To learn how to create your own instance of see the initialization documentation article. You will then pass this instance into a root component.

For convenience is exported by from the core Apollo Client package.

To see the full API documentation for the class go to the core documentation site.





const client = new ApolloClient({




import { createNetworkInterface } from'react-apollo';

The function creates a simple HTTP network interface using the provided configuration object which includes the URI Apollo will use to fetch GraphQL from.

For convenience is exported by from the core Apollo Client package.

To learn more about and network interfaces in general go to the core documentation site.





const networkInterface = createNetworkInterface({

uri: '/graphql',


Client management

React-Apollo includes a component for providing a client instance to a React component tree, and a higher-order component for retrieving that client instance.


import { ApolloProvider } from'react-apollo';

Makes the GraphQL client available to any of your components enhanced by the function. The component works the same as the component. It provides an instance to all of your GraphQL components that either use the function, or the function. You may also provide your Redux store using the component in addition to providing your GraphQL client.

If you do not add this component to the root of your React tree then your components enhanced with Apollo capabilities will not be able to function.

To learn more about initializing an instance of , be sure to read the setup and options guide.

The component takes the following props:

  • : The required instance. This instance will be used by all of your components enhanced with GraphQL capabilties.
  • : This is an optional instance of a Redux store. If you choose to pass in your Redux store here then will also provide your Redux store like the component. This means you only need to use one provider component instead of two!

If you want to get direct access to your instance that is provided by in your components then be sure to look at the enhancer function.









<ApolloProvider client={client}>

<MyRootComponent />





import { withApollo } from'react-apollo';

A simple enhancer which provides direct access to your instance. This is useful if you want to do custom logic with Apollo. Such as calling one-off queries. By calling this function with the component you want to enhance, will create a new component which passes in an instance of as a prop.

If you are wondering when to use and when to use the answer is that most of the time you will want to use . provides many of the advanced features you need to work with your GraphQL data. You should only use if you want the GraphQL client without any of the other features.

This will only be able to provide access to your client if there is an component higher up in your tree to actually provide the client.







exportdefault withApollo(MyComponent);

functionMyComponent({ client }) {



Sours: https://s3.amazonaws.com/apollo-docs-1.x/api.html
Apollo's Space Mission - Space Documentary 2019 [HD]

Apollo Client

Apollo Client

npm versionBuild StatusJoin the community

Apollo Client is a fully-featured caching GraphQL client with integrations for React, Angular, and more. It allows you to easily build UI components that fetch data via GraphQL.


All Apollo Client documentation, including React integration articles and helpful recipes, can be found at:

The Apollo Client API reference can be found at:

Learn how to use Apollo Client with self-paced hands-on training on Odyssey, Apollo's official learning platform:


Who is Apollo?

Apollo builds open-source software and a graph platform to unify GraphQL across your apps and services. We help you ship faster with:

  • Apollo Studio – A free, end-to-end platform for managing your GraphQL lifecycle. Track your GraphQL schemas in a hosted registry to create a source of truth for everything in your graph. Studio provides an IDE (Apollo Explorer) so you can explore data, collaborate on queries, observe usage, and safely make schema changes.
  • Apollo Federation – The industry-standard open architecture for building a distributed graph. Use Apollo’s open-source gateway to compose a unified graph from multiple subgraphs, determine a query plan, and route requests across your services.
  • Apollo Client – The most popular GraphQL client for the web. Apollo also builds and maintains Apollo iOS and Apollo Android.
  • Apollo Server – A production-ready JavaScript GraphQL server that connects to any microservice, API, or database. Compatible with all popular JavaScript frameworks and deployable in serverless environments.

Learn how to build with Apollo

Check out the Odyssey learning platform, the perfect place to start your GraphQL journey with videos and interactive code challenges. Join the Apollo Community to interact with and get technical help from the GraphQL community.

Sours: https://github.com/apollographql/apollo-client

You will also like:

I'll substitute the duck now. Victor began to pull his limp penis out of the girl's ass. Julia struggled to squeeze her back hole.

1021 1022 1023 1024 1025