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

graphql / graphql-js / 479
99%
master: 98%

Build:
Build:
LAST BUILD BRANCH: directives
DEFAULT BRANCH: master
Ran 31 Aug 2015 10:52PM UTC
Jobs 1
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

pending completion
479

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.

7 of 7 new or added lines in 2 files covered. (100.0%)

4908 of 4945 relevant lines covered (99.25%)

4160.75 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
5
100.0
src/language/parser.js

Uncovered Existing Lines

Lines Coverage ∆ File
2
100.0
src/language/parser.js
Jobs
ID Job ID Ran Files Coverage
1 479.1 31 Aug 2015 10:52PM UTC 0
99.25
Travis Job 479.1
Source Files on build 479
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #479
  • a68212ee on github
  • Prev Build on rfc-type-extension (#473)
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

© 2025 Coveralls, Inc