GithubHelp home page GithubHelp logo

jamesgorman2 / graphql-type-repository Goto Github PK

View Code? Open in Web Editor NEW
2.0 2.0 0.0 572 KB

A repository for assembling named GraphQL types and schemas from modules

License: Other

JavaScript 98.00% Shell 1.05% Python 0.95%

graphql-type-repository's Introduction

graphql-type-repository

A repository for assembling GraphQL types and schemas from modules.

npm version Build Status Coverage Status

graphql-type-repository provides a repository for assembling GraphQL types and schemas for (GraphQL.js)[https://github.com/graphql/graphql-js]. It's goal is to provide additional checking to safely modularise a GraphQL schema specified in the GraphQL schema language.

TODO

  • finish decorators
  • new decorator to check input/ouputness of fields/arguments
  • finish schema builder
  • finish root class and config
  • fix this page
  • example server
  • wiki with more detail on why this exists
  • wiki with more detail on how to build things
  • wiki with more detail on the internal details
  • use Module to get type so we can register refs from raw types
  • panic checking for unexpected state
  • extend raw types
  • fix up tests
  • fix up naming in lambdas

Getting Started

Using graphql-type-repository

Install graphql-type-repository from npm

npm install --save graphql-type-repository graphql-js

or

yarn add graphql-type-repository graphql-js

Note that graphql-js is a peer dependency and must be installed separately.

Node support

graphql-type-repository is tested against node 4, 6 and 7. It uses (Babel)[https://babeljs.io/] to convert es6 to es6-node.

Want to ride the bleeding edge?

The npm branch in this repository is automatically maintained to be the last commit to master to pass all tests, in the same form found on npm. It is recommend to use builds deployed npm for many reasons, but if you want to use the latest not-yet-released version of graphql-type-repository, you can do so by depending directly on this branch:

npm install graphql@git://github.com/jamesgorman2/graphql-type-repository.git#npm

Contributing

We actively welcome pull requests, learn how to contribute.

Changelog

Changes are tracked as Github releases.

License

GraphQL is BSD-licensed.

Build steps and CONTRIBUTING.md are modified from (GraphQL.js)[https://github.com/graphql/graphql-js] under the same license.

Code example

personModule.js

import {
  Module,
} from 'graphql-type-repository';

import personResolvers from './personResolvers';

export default const personModule: Module = new Module('Person')
  .withSchema(`
type Name {
  firstName: String!
  lastName: String!
}
type Person {
  id: ID!
  name: Name
  age: Int
}
type PersonQuery {
  getPersonById(id: ID!): Person
}
schema {
  query PersonQuery
}`,
  personResolvers,
);

propertyModule.js

import {
  GraphQLString,
  GraphQLObjectType,
} from 'graphql';

import {
  Module,
} from 'graphql-type-repository';

import propertyResolvers from './propertyResolvers';

export default const propertyModule: Module = new Module('Property')
  .withType(
    new GraphQLObjectType({
      name: 'Address',
      fields: {
        street: { type: GraphQLString },
        postCode: { type: GraphQLString },
      },
    })
  )
  .withSchema(`
type Property {
  id: ID!
  address: Address
  occupants: [Person]
}
extend type Person {
  livesAt: Property
}
type PropertyQuery {
  getPropertyById(id: ID!): Property
}
schema {
  query PropertyQuery
}`,
  propertyResolvers,
);

buildSchema.js

import {
  TypeRepository,
} from 'graphql-type-repository';

import personModule from './personModule';
import propertyModule from './propertyModule';

export const schema = new TypeRepository()
  .add(personModule)
  .add(propertyModule)
  .getSchema({ query: 'Query' });

Effective schema

type Name {
  firstName: String!
  lastName: String!
}
type Person {
  id: ID!
  name: Name
  age: Int
  livesAt: Property
}
type Address {
  street: String
  postCode: String
}
type Property {
  id: ID!
  address: Address
  occupants: [Person]
}
type Query {
  getPersonById(id: ID!): Person
  getPropertyById(id: ID!): Property
}
schema {
  query Query
}

Internal repository execution

const internalRepository: ModuleRepository = new ModuleRepository()
  .withModule(personModule)
  .withModule(propertyModule);

const parsedTypeGraph: FlattenedTypeGraph = FlattenedTypeGraph.from(internalRepository)
  .map(appendSystemTypes)
  .map(appendSystemDirectives)
  .map(assertNoSystemTypesDefinedByUser)
  .map(assertNoSystemDirectivesDefinedByUser)

  .map(assertNoModuleRepositoryErrors)
  .map(assertNoModuleErrors)

  .map(assertNoMissingTypes)
  .map(assertNoDuplicateTypes)
  .map(assertNoDuplicateExtensionFields)
  .map(assertNoDuplicateSchemaFields)
  .map(assertNoMissingSchemaResolvers)
  .map(assertNoDisconnectedSubgraphs)

  .map(assertNoDuplicateDirectives)
  .map(assertNoMissingDirectives)
  .map(assertNoUnusedDirectives)

  .map(generateTypes);

const schema: GraphQLSchema = parsedTypeGraph.getSchema({ query: 'Query' });

graphql-type-repository's People

Contributors

greenkeeper[bot] avatar jamesgorman2 avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

graphql-type-repository's Issues

An in-range update of flow-bin is breaking the build 🚨

Version 0.43.1 of flow-bin just got published.

Branch Build failing 🚨
Dependency flow-bin
Current Version 0.43.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As flow-bin is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 1 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of jest is breaking the build 🚨

Version 18.1.0 of jest just got published.

Branch Build failing 🚨
Dependency jest
Current Version 18.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As jest is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-preset-latest is breaking the build 🚨

Version 6.24.1 of babel-preset-latest just got published.

Branch Build failing 🚨
Dependency babel-preset-latest
Current Version 6.24.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-latest is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.3.0 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 46 commits.

  • b79e083 Merge pull request #837 from benmosher/release-2.3.0
  • 74425a2 changelog update for 2.3.0
  • 1377f55 bump v2.3.0
  • 2efc41a fix null pointer exception (#717) (#797)
  • 0fb592e Add support to specify the package.json (#685)
  • 2cc9768 Add test for flow type export (#835)
  • bd0e5e3 Merge pull request #821 from smably/patch-1
  • 412e518 Clarify docs for glob arrays
  • 106740f chore(package): update typescript-eslint-parser to version 2.1.0 (#790)
  • 6288cf9 chore(package): update babel-register to version 6.24.1 (#796)
  • 2e9eea6 newline-after-import test syntax fails
  • c9f10e8 extensions test fixes, attempt 2
  • 861765f fix babel syntax errors in extensions tests
  • 82f796c chore(package): update cross-env to version 4.0.0 (#783)
  • 98e7048 Merge pull request #757 from gmathieu/fix-default-keyword

There are 46 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-preset-es2017 is breaking the build 🚨

Version 6.24.1 of babel-preset-es2017 just got published.

Branch Build failing 🚨
Dependency babel-preset-es2017
Current Version 6.22.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-es2017 is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-preset-es2015 is breaking the build 🚨

Version 6.22.0 of babel-preset-es2015 just got published.

Branch Build failing 🚨
Dependency babel-preset-es2015
Current Version 6.18.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-es2015 is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details

  • continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

Version 7.2.3 of babel-eslint just got published.

Branch Build failing 🚨
Dependency babel-eslint
Current Version 7.2.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/jamesgorman2/graphql-type-repository/builds/224521250)

Commits

The new version differs by 2 commits0.

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint-config-airbnb-base is breaking the build 🚨

Version 11.1.0 of eslint-config-airbnb-base just got published.

Branch Build failing 🚨
Dependency eslint-config-airbnb-base
Current Version 11.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-airbnb-base is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of coveralls is breaking the build 🚨

Version 2.12.0 of coveralls just got published.

Branch Build failing 🚨
Dependency coveralls
Current Version 2.11.16
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details

  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes Branch coverage support

Adds branch coverage data to Coveralls API post.

Commits

The new version differs by 2 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

Version 7.2.2 of babel-eslint just got published.

Branch Build failing 🚨
Dependency babel-eslint
Current Version 7.2.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v7.2.2

v7.2.2


  • Fix: use eslint-scope instead of escope if present (#461) (Vitor Balocco)
  • Separate finding peer deps from monkeypatching (#460) (Andres Suarez)
  • Remove unused .gitmodules (#457) (Andres Suarez)
  • Use dedent for unpadding (#456) (Andres Suarez)
  • Enable strict mode in all of babylon-to-espree (Andres Suarez)
  • Move ast convert steps to babylon-to-espree (Andres Suarez)
  • Use for-loop for template literal conversion (Andres Suarez)
  • Only iterate over tokens once (Andres Suarez)
  • Inline fixDirectives and use for-loop (Andres Suarez)
  • Consolidate versions of "convertComments" (Andres Suarez)
  • toAst pass "source" in state instead of keeping in scope (Andres Suarez)
  • Add type parameter scope tests (#454) (Andres Suarez)
Commits

The new version differs by 14 commits .

  • f59d200 7.2.2
  • 8622009 Fix: use eslint-scope instead of escope if present (#461)
  • 0f611b8 Separate finding peer deps from monkeypatching (#460)
  • 1201e12 Remove unused .gitmodules (#457)
  • a750684 Use dedent for unpadding (#456)
  • cdb92fe Merge pull request #455 from babel/babylon-to-espree-tidy
  • ec14787 Enable strict mode in all of babylon-to-espree
  • 6c5beec Move ast convert steps to babylon-to-espree
  • d2ce789 Use for-loop for template literal conversion
  • 539af05 Only iterate over tokens once
  • 06c3a31 Inline fixDirectives and use for-loop
  • 5d32ad0 Consolidate versions of "convertComments"
  • 2541fc9 toAst pass "source" in state instead of keeping in scope
  • 21dac73 Add type parameter scope tests (#454)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of graphql is breaking the build 🚨

Version 0.9.2 of graphql just got published.

Branch Build failing 🚨
Dependency graphql
Current Version 0.9.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As graphql is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 88 commits .

  • 5ba817e 0.9.2
  • 7656015 Freshen yarn.lock
  • a61f8e2 Merge pull request #774 from graphql/greenkeeper/coveralls-2.13.0
  • 2c6bab2 chore(package): update coveralls to version 2.13.0
  • 14ec456 Merge pull request #769 from wincent/glh/node
  • cdb9af2 Don't run on Node 0.12 in Travis
  • dcae89d Freshen yarn.lock
  • 4e49ac6 Merge pull request #768 from graphql/greenkeeper/babel-eslint-7.2.1
  • a41b700 chore(package): update babel-eslint to version 7.2.1
  • fa4c8e3 Merge pull request #767 from neelance/master
  • ba401e1 Unify wording in error messages.
  • 2c8d565 Freshen yarn.lock
  • 2f56f17 Merge pull request #766 from graphql/greenkeeper/eslint-plugin-flowtype-2.30.4
  • 275e967 chore(package): update eslint-plugin-flowtype to version 2.30.4
  • 94e2431 Freshen yarn.lock

There are 88 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-cli is breaking the build 🚨

Version 6.23.0 of babel-cli just got published.

Branch Build failing 🚨
Dependency babel-cli
Current Version 6.22.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details

  • continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-babel is breaking the build 🚨

Version 4.1.2 of eslint-plugin-babel just got published.

Branch Build failing 🚨
Dependency eslint-plugin-babel
Current Version 4.1.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-babel is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v4.1.2

Bug Fix

babel/semi: doesn't fail when using for await (let something of {}). Includes class properties

Commits

The new version differs by 2 commits.

  • 1eab147 4.1.2
  • 9468524 Modifying semi rule to support for await (#126)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 3.13.0 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 3.12.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes v3.13.0
  • cd4c025 Update: add fixer for no-extra-label (#7840) (Teddy Katz)
  • aa75c92 Fix: Ensure prefer-const fixes destructuring assignments (fixes #7852) (#7859) (Teddy Katz)
  • 4008022 Chore: Refactor to use ES6 Classes (Part 3)(refs #7849) (#7865) (Gyandeep Singh)
  • c9ba40a Update: add fixer for no-unneeded-ternary (#7540) (Teddy Katz)
  • dd56d87 Update: add object-shorthand option for arrow functions (fixes #7564) (#7746) (Teddy Katz)
  • fbafdc0 Docs: padded-blocks never case (fixes #7868) (#7878) (alberto)
  • ca1f841 Fix: no-useless-return stack overflow on loops after throw (fixes #7855) (#7856) (Teddy Katz)
  • d80d994 Update: add fixer for object-property-newline (fixes #7740) (#7808) (Teddy Katz)
  • bf3ea3a Fix: capitalized-comments: Ignore consec. comments if first is invalid (#7835) (Kevin Partington)
  • 616611a Chore: Refactor to use ES6 Classes (Part 2)(refs #7849) (#7847) (Gyandeep Singh)
  • 856084b Chore: Refactor to use ES6 Classes (Part 1)(refs #7849) (#7846) (Gyandeep Singh)
  • bf45893 Docs: Clarify that we only support Stage 4 proposals (#7845) (Kevin Partington)
  • 0fc24f7 Fix: adapt new-paren rule so it handles TypeScript (fixes #7817) (#7820) (Philipp A)
  • df0b06b Fix: no-multiple-empty-lines perf issue on large files (fixes #7803) (#7843) (Teddy Katz)
  • 18fa521 Chore: use ast-utils helper functions in no-multiple-empty-lines (#7842) (Teddy Katz)
  • 7122205 Docs: Array destructuring example for no-unused-vars (fixes #7838) (#7839) (Remco Haszing)
  • e21b36b Chore: add integration tests for cache files (refs #7748) (#7794) (Teddy Katz)
  • 2322733 Fix: Throw error if ruletester is missing required test scenarios (#7388) (Teddy Katz)
  • 1beecec Update: add fixer for operator-linebreak (#7702) (Teddy Katz)
  • c5c3b21 Fix: no-implied-eval false positive on 'setTimeoutFoo' (fixes #7821) (#7836) (Teddy Katz)
  • 00dd96c Chore: enable array-bracket-spacing on ESLint codebase (#7830) (Teddy Katz)
  • ebcae1f Update: no-return-await with with complex return argument (fixes #7594) (#7595) (Dalton Santos)
  • fd4cd3b Fix: Disable no-var autofixer in some incorrect cases in loops (#7811) (Alan Pierce)
  • 1f25834 Docs: update outdated info in Architecture page (#7816) (Teddy Katz)
  • f20b9e9 Fix: Relax no-useless-escape's handling of ']' in regexes (fixes #7789) (#7793) (Teddy Katz)
  • 3004c1e Fix: consistent-return shouldn't report class constructors (fixes #7790) (#7797) (Teddy Katz)
  • b938f1f Docs: Add an example for the spread operator to prefer-spread.md (#7802) (#7804) (butlermd)
  • b8ce2dc Docs: Remove .html extensions from links in developer-guide (#7805) (Kevin Partington)
  • aafebb2 Docs: Wrap placeholder sample in {% raw %} (#7798) (Daniel Lo Nigro)
  • bb6b73b Chore: replace unnecessary function callbacks with arrow functions (#7795) (Teddy Katz)
  • 428fbdf Fix: func-call-spacing "never" doesn't fix w/ line breaks (fixes #7787) (#7788) (Kevin Partington)
  • 6e61070 Fix: semi false positive before regex/template literals (fixes #7782) (#7783) (Teddy Katz)
  • ff0c050 Fix: remove internal property from config generation (fixes #7758) (#7761) (alberto)
  • 27424cb New: prefer-destructuring rule (fixes #6053) (#7741) (Alex LaFroscia)
  • bb648ce Docs: fix unclear example for no-useless-escape (#7781) (Teddy Katz)
  • 8c3a962 Fix: syntax errors from object-shorthand autofix (fixes #7744) (#7745) (Teddy Katz)
  • 8b296a2 Docs: fix in semi.md: correct instead of incorrect (#7779) (German Prostakov)
  • 3493241 Upgrade: strip-json-comments ~v2.0.1 (Janus Troelsen)
  • 75b7ba4 Chore: enable object-curly-spacing on ESLint codebase (refs #7725) (#7770) (Teddy Katz)
  • 7d1dc7e Update: Make default-case comment case-insensitive (fixes #7673) (#7742) (Robert Rossmann)
  • f1bf5ec Chore: convert remaining old-style context.report() calls to the new API (#7763) (Teddy Katz)
Commits

The new version differs by 43 commits .

  • 8571ab8 3.13.0
  • d54e0c1 Build: package.json and changelog update for 3.13.0
  • cd4c025 Update: add fixer for no-extra-label (#7840)
  • aa75c92 Fix: Ensure prefer-const fixes destructuring assignments (fixes #7852) (#7859)
  • 4008022 Chore: Refactor to use ES6 Classes (Part 3)(refs #7849) (#7865)
  • c9ba40a Update: add fixer for no-unneeded-ternary (#7540)
  • dd56d87 Update: add object-shorthand option for arrow functions (fixes #7564) (#7746)
  • fbafdc0 Docs: padded-blocks never case (fixes #7868) (#7878)
  • ca1f841 Fix: no-useless-return stack overflow on loops after throw (fixes #7855) (#7856)
  • d80d994 Update: add fixer for object-property-newline (fixes #7740) (#7808)
  • bf3ea3a Fix: capitalized-comments: Ignore consec. comments if first is invalid (#7835)
  • 616611a Chore: Refactor to use ES6 Classes (Part 2)(refs #7849) (#7847)
  • 856084b Chore: Refactor to use ES6 Classes (Part 1)(refs #7849) (#7846)
  • bf45893 Docs: Clarify that we only support Stage 4 proposals (#7845)
  • 0fc24f7 Fix: adapt new-paren rule so it handles TypeScript (fixes #7817) (#7820)

There are 43 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-polyfill is breaking the build 🚨

Version 6.26.0 of babel-polyfill just got published.

Branch Build failing 🚨
Dependency babel-polyfill
Current Version 6.23.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-polyfill is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-preset-stage-0 is breaking the build 🚨

Version 6.24.1 of babel-preset-stage-0 just got published.

Branch Build failing 🚨
Dependency babel-preset-stage-0
Current Version 6.22.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-preset-stage-0 is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.