title: Introspection query for EnumValues as a GraphQL fragment in react-component
body: <p>I'm building a React Native application using GraphQL (Hosted on graph.cool) with a Relay Schema. 
  I have a QueryRenderer in the top-level component, fetching data for the presentational components using fragments, which is working fine. </p>
  
  <p>My problem: I want to do an introspection query to fetch possible enum values as a list, for a specific field in my schema and fetch these alongside the fragments.
  My current query with fragments:</p>
  
  <pre><code>query ReportingContainerQuery {
      viewer {
          ...MainList_items
             ...
      }
  }
  </code></pre>
  
  <p>The MainList_items fragment:</p>
  
  <pre><code>fragment AnimalList_items on Viewer {
      allAnimalCategories {
          edges {
              node{
                  id
                  ...AnimalListRow_item
              }
          }
      }
  }
  </code></pre>
  
  <p>I got the following query working for fetching enumValues via introspection (using: <a href="https://www.graph.cool/forum/t/how-to-access-the-possible-values-of-an-enum-type-created-inside-the-console/23/2" rel="nofollow noreferrer">https://www.graph.cool/forum/t/how-to-access-the-possible-values-of-an-enum-type-created-inside-the-console/23/2</a>):</p>
  
  <pre><code>query {
      __type(name: "JOURNAL_ENTRY_GENDER") {
          enumValues {
              name
          }
      }
  }
  </code></pre>
  
  <p>But i can't seem to find a way to create a fragment that can be added to the top-level query.
  I could just paste the introspection directly into the top-level query, but that would kind of work against the relay framework, as far as I understand it. Since doing it this way I would have to explicitly pass the result down as a props, instead of letting the presentational component specify what it needs and supplying that as a fragment to the QueryRenderer at the top-level and letting the relay framework implicitly pass the query result down to the component.</p>