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

graphql / graphql-js / 1165
98%

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

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

Jobs
ID Job ID Ran Files Coverage
1 1165.1 25 Aug 2016 02:26AM UTC 0
98.24
Travis Job 1165.1
Source Files on build 1165
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #1165
  • 5e3d377e on github
  • Prev Build on master (#1157)
  • Next Build on master (#1166)
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