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

graphql / graphql-js / 1165 / 1
98%
master: 98%

Build:
DEFAULT BRANCH: master
Ran 25 Aug 2016 02:26AM UTC
Files 138
Run time 13s
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

25 Aug 2016 02:20AM UTC coverage: 98.24% (-0.05%) from 98.289%
1165.1

push

travis-ci

web-flow
Advantage common convention for naming root types. (#470)

This is a result of a conversation I had with @lacker that we should provide a stronger opinion on what to name the root types, and then advantage that opinion. Here's the result of that:

If you use the type names `Query` and `Mutation` for your root types, then printing the schema or parsing a schema IDL can omit the `schema { query: Query, mutation: Mutation }` boilerplate. If your root type names are anything other than these, then you have to include it.

There doesn't seem to be a significant downsite to this except for the relative complication of understanding why sometimes a `schema {}` description is included and sometimes it isn't.

7422 of 7555 relevant lines covered (98.24%)

1398.7 hits per line

Source Files on job 1165.1
  • Tree
  • List 0
  • Changed 8
  • Source Changed 4
  • Coverage Changed 8
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1165
  • Travis Job 1165.1
  • 5e3d377e on github
  • Prev Job for on master (#1157.1)
  • Next Job for on master (#1166.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