• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

graphql / graphql-js / 473 / 1
99%
master: 98%

Build:
Build:
LAST BUILD BRANCH: directives
DEFAULT BRANCH: master
Ran 31 Aug 2015 10:34PM UTC
Files 115
Run time 3s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

31 Aug 2015 10:23PM UTC coverage: 99.252%. First build
473.1

push

travis-ci

leebyron
[RFC] Type extension syntax

This proposal introduces a syntactic addition for client-side tools that perform code generation. It allows those tools to describe "extensions" to the server-supplied GraphQL schema. Tools may then use this information to generate client side Plain-Ol'-Data types which include these client-side-only extensions.

The syntax I'm proposing is:

```
TypeExtensionDefinition : `extend` ObjectDefinition
```

An example of this might look like:

```
type User {
  name: String
  birthday: Int
}

extend type User {
  age: Int
}
```

While I could have proposed simply `extend User { ... }`, I chose to fully reuse the ObjectDefinition rule to preserve the future ability to expand this syntax to include extending interfaces, enums, and other types.

4908 of 4945 relevant lines covered (99.25%)

4160.75 hits per line

Source Files on job 473.1
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 473
  • Travis Job 473.1
  • 485bfe98 on github
  • Next Job for on rfc-type-extension (#479.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc