I think READMEs will often want to describe their schema in GraphQL form, like so:

type Comment {
  postedBy: User!
  createdAt: String! # Actually a date
  content: String!
}

type Entry {
  repository: Repository!
  postedBy: User!
  createdAt: String! # Actually a date
  score: Int!
  comments: [Comment]! # Should this be paginated?
  commentCount: Int!
}

As you can see, comments and arguments are highlighted but not other stuff. It would be cool to highlight for example the type keyword, the types, etc.

Hi, the latest GraphQL spec updated the description syntax: graphql/graphql-js#927. This is not supported by the current syntax highlighting. An example:

"""
Description that is

spanning multiple lines
"""
type Test {
   "Field description"
   field: String
}

The current comment element is here: https://github.com/rmosolgo/language-graphql/blob/master/grammars/graphql.json#L162-L169 but for backwards compatibility, I think two new elements (descriptionline and descriptionblock) might be best?

as of graphql 0.12.3 you can now add comments as string literals

"This is a description."
schema {
    query: Query
}

if we could highlight this somehow, maybe even as comments. note: they can be multi line.

The current release available from the Atom module registry is still 0.2.0. How do we go about getting the latest version published there?

GraphQL comments syntax has changed and is now using a triple double-quotes characters format. This breaks syntax highlighting on GitHub.

Example on GitHub: https://gist.github.com/Akryum/74471ad4789e4fcde6e072ea0605c62b

@rmosolgo - Apologies for opening an issue; I wanted to chat with you about us collaborating to develop Nuclide GraphQL language service, but couldn't find a viable contact information. Would you be interested in working together to provide Nuclide/Atom language service?

Let me know what you think!

Is there a way to configure this package so that it would highlight <page-query> and <static-query> tags within Vue templates?

Can you publish this to npm as atom-language-graphql so that it can be used with highlights?

Thanks for a nice package 👍

I really love a good CHANGELOG to get to know what's new in a version, but what's worse than no CHANGELOG is an outdated one – especially for an Atom package as Atom itself highlights the CHANGELOG on the package's page in the app.

As it looks like the CHANGELOG is no longer intended to be updated, then it should in my opinion be removed.

Is there a way to specify for what file types I want this syntax to be active?

See:

Or:

Commas are optional in GraphQL.

This doesn't seem to be an issue with language-babel.

As discussed with @gandm and @rmosolgo in this issue, we should migrate to this repo and publish it to npm/apm. I think I can do the copy/paste myself, but I'd need some help publishing this to npm/apm I guess :)

Creating issue to track progress.

Example (from the graphql-yoga project): link.

Definition of docstring: link.

v0.6.0 is still available here, is this right?
https://atom.io/packages/atom-language-graphql

Problem

Highlighting fails inside the enum declaration. Everything wants to be orange.

Screenshot

Testing code

type ApprovalRequirements {
    approval_list_required: Boolean @doc(description: "Require approval if items are not in a list.")
    approval_subtotal: Float @doc(description: "Dollar amount. Theshold determined when 'Sometimes require approval' is set.")
    approver_id: ID @doc(description: "Entity ID of the user who approves.")
    requires_approval: RequiresApprovalEnum! @doc(description: "")
}

enum RequiresApprovalEnum @doc(description: "State for when approval is required, which determines approval conditions.") {
    ALWAYS @doc(description: "Always require approval")
    NEVER @doc(description: "Does not require approval")
    SOMETIMES @doc(description: "Sometimes require approval")
}

@connection(key: "Posts_allPosts") { invokes error "Unknown directive "connection""

export default createFragmentContainer(
  Posts,
  graphql`
    fragment Posts_viewer on Viewer {
      allPosts(first: $first, orderBy: createdAt_DESC)
        @connection(key: "Posts_allPosts") {
        edges {
          node {
            id
            ...Post_post
          }
        }
      }
      # To understand what's happening here:
      # Post_viewer fragment will be attached to viewer.__fragments for Post.js
      ...Post_viewer
    }
  `,
);