Git Product home page Git Product logo

data-source-base's People

Contributors

corycook avatar greenkeeper[bot] avatar jlengstorf avatar kbrandwijk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

data-source-base's Issues

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 @gramps/cli is breaking the build 🚨

The devDependency @gramps/cli was updated from 1.4.0 to 1.5.0.

🚨 View failing branch.

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

@gramps/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

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 🌴

Include schema file in build output

Currently, the schema file is read in the index file, and injected by babel. The .graphql file itself is not included in the build. In order to generate compile-time bindings when using a datasource, the schema file itself is needed. Can this be included in the build output by default?

An in-range update of @gramps/gramps is breaking the build 🚨

The devDependency @gramps/gramps was updated from 1.4.0 to 1.5.0.

🚨 View failing branch.

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

@gramps/gramps is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v1.5.0

1.5.0 (2018-10-17)

Features

Commits

The new version differs by 1 commits.

  • 9bf76af feat: add Upload scalar/resolver (#107)

See the full diff

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 🌴

Unexpected token ")" when checking out the project

Hi everyone,

I'm playing around with GrAMPS, so trying the first 3 commands:

# 💥 zero dependencies! no global installs! create a new data source
npx graphql-cli create -b gramps-graphql/data-source-base data-source-mydata

# 📂 move into the newly-created data source
cd $_

# 🚀 start the GraphQL Playground with your spankin’ new data source
yarn dev

I got this issue when running the first command npx graphql-cli create -b gramps-graphql/data-source-base data-source-mydata

npx: installed 394 in 102.974s
<my-folder-info-deleted-for-privacy>\npm-cache\_npx\192\node_modules\graphql-cli\dist\bi
n.js
[graphql create] Downloading boilerplate from https://github.com/gramps-graphql/
data-source-base/archive/master.zip...
[graphql create] Installing node dependencies for <my-folder-info-deleted-for-privacy>\data-source-stitchingtest\package.json...
yarn install v1.3.2
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check.
Excluding it from installation.
[3/4] Linking dependencies...
warning "@gramps/cli > apollo-server-express > apollo-server-core > apollo-cache
[email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0".
warning "@gramps/cli > apollo-server-express > apollo-server-core > apollo-traci
[email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0".
warning "@gramps/cli > apollo-server-express > apollo-server-core > graphql-exte
[email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0".
warning " > [email protected]" has unmet peer dependency "babel-core@^6.0.0 || ^
7.0.0-0".
[4/4] Building fresh packages...
[-/2] ? waiting...
[2/2] ? weak: Building the projects in this solution one at a time. To
[-/2] ? waiting...
[-/2] ? waiting...
warning Error running install script for optional dependency: "<my-folder-info-deleted-for-privacy>\\data-source-stitchingtest\\node_modules\
\weak: Command failed.\nExit code: 1\nCommand: node-gyp rebuild\nArguments: \nDi
rectory:<my-folder-info-deleted-for-privacy>\\data-source-st
itchingtest\\node_modules\\weak\nOutput:\n<my-folder-info-deleted-for-privacy>\\data-source-stitchingtest\\node_modules\\weak>if not defined
npm_config_node_gyp (node \"C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\n
ode-gyp-bin\\\\..\\..\\node_modules\\node-gyp\\bin\\node-gyp.js\" rebuild )  els
e (node \"\" rebuild ) \r\ngyp info it worked if it ends with ok\ngyp info using
 [email protected]\ngyp info using [email protected] | win32 | x64\ngyp info spawn C:\\Py
thon27\\python.exe\ngyp info spawn args [ 'C:\\\\Program Files\\\\nodejs\\\\node
_modules\\\\npm\\\\node_modules\\\\node-gyp\\\\gyp\\\\gyp_main.py',\ngyp info sp
awn args   'binding.gyp',\ngyp info spawn args   '-f',\ngyp info spawn args   'm
svs',\ngyp info spawn args   '-G',\ngyp info spawn args   'msvs_version=auto',\n
gyp info spawn args   '-I',\ngyp info spawn args   <my-folder-info-deleted-for-privacy>\\\\data-source-stitchingtest\\\\node_modul
es\\\\weak\\\\build\\\\config.gypi',\ngyp info spawn args   '-I',\ngyp info spaw
n args   'C:\\\\Program Files\\\\nodejs\\\\node_modules\\\\npm\\\\node_modules\\
\\node-gyp\\\\addon.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   '
<my-folder-info-deleted-for-privacy>\\\\.node-gyp\\\\6.10.3\\\\include\\\\node\\\\common.gypi',\ng
yp info spawn args   '-Dlibrary=shared_library',\ngyp info spawn args   '-Dvisib
ility=default',\ngyp info spawn args   '-Dnode_root_dir=<my-folder-info-deleted-for-privacy>\\\\.n
ode-gyp\\\\6.10.3',\ngyp info spawn args   '-Dnode_gyp_dir=C:\\\\Program Files\\
\\nodejs\\\\node_modules\\\\npm\\\\node_modules\\\\node-gyp',\ngyp info spawn ar
gs   '-Dnode_lib_file=node.lib',\ngyp info spawn args   '-Dmodule_root_dir=<my-folder-info-deleted-for-privacy>\\\\data-source-stit
chingtest\\\\node_modules\\\\weak',\ngyp info spawn args   '--depth=.',\ngyp inf
o spawn args   '--no-parallel',\ngyp info spawn args   '--generator-output',\ngy
p info spawn args   '<my-folder-info-deleted-for-privacy>\\\\data-source-stitchingtest\\\\node_modules\\\\weak\\\\build',\ngyp info
 spawn args   '-Goutput_dir=.' ]\ngyp info spawn C:\\Windows\\Microsoft.NET\\Fra
mework\\v4.0.30319\\msbuild.exe\ngyp info spawn args [ 'build/binding.sln',\ngyp
 info spawn args   '/clp:Verbosity=minimal',\ngyp info spawn args   '/nologo',\n
gyp info spawn args   '/p:Configuration=Release;Platform=x64' ]\nBuilding the pr
ojects in this solution one at a time. To enable parallel build, please add the
\"/m\" switch.\r\nMSBUILD : error MSB3428: Could not load the Visual C++ compone
nt \"VCBuild.exe\". To fix this, 1) install the .NET Framework 2.0 SDK, 2) insta
ll Microsoft Visual Studio 2005 or 3) add the location of the component to the s
ystem path if it is installed elsewhere.  [<my-folder-info-deleted-for-privacy>\\data-source-stitchingtest\\node_modules\\weak\\build\\bindin
g.sln]\r\ngyp ERR! build error \ngyp ERR! stack Error: `C:\\Windows\\Microsoft.N
ET\\Framework\\v4.0.30319\\msbuild.exe` failed with exit code: 1\ngyp ERR! stack
     at ChildProcess.onExit (C:\\Program Files\\nodejs\\node_modules\\npm\\node_
modules\\node-gyp\\lib\\build.js:276:23)\ngyp ERR! stack     at emitTwo (events.
js:106:13)\ngyp ERR! stack     at ChildProcess.emit (events.js:191:7)\ngyp ERR!
stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:
12)\ngyp ERR! System Windows_NT 6.1.7601\ngyp ERR! command \"C:\\\\Program Files
\\\\nodejs\\\\node.exe\" \"C:\\\\Program Files\\\\nodejs\\\\node_modules\\\\npm\
\\\node_modules\\\\node-gyp\\\\bin\\\\node-gyp.js\" \"rebuild\"\ngyp ERR! cwd C:
Done in 55.10s.
[graphql create] Running boilerplate install script...
x
Unexpected token )

It seems like there are multiple errors going on here (one with .NET framework, and the other with the unexpected token).
When I proceeded to run yarn dev, it throws the unexpected token again:

yarn run v1.3.2
$ gramps dev --data-source .
<my-folder-info-deleted-for-privacy>\data-source-stitchingtest\nod
e_modules\@gramps\cli\bin\dev.js:78
    )
    ^
SyntaxError: Unexpected token )
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.extWrap (<my-folder-info-deleted-for-privacy>\data-s
ource-stitchingtest\node_modules\reify\node\compile-hook.js:59:7)
    at Object.extManager (<my-folder-info-deleted-for-privacy>\dat
a-source-stitchingtest\node_modules\reify\node\compile-hook.js:19:12)
    at Object.manager [as .js] <my-folder-info-deleted-for-privacy>\data-source-stitchingtest\node_modules\reify\node\wrapper.js:108:20)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this comm
and.

I looked at the file at node_modules@gramps\cli\bin\dev.js:78. It doesn't seem like an unexpected token. Does anyone have any idea what might have caused this?

REST Boilerplate

Hi,

I think most folks using this will want to use it to integrate existing REST APIs to take advantage of schema remix/stitching and to expose sources as as single GraphQL end point.

Would love to see a boilerplate to generate scaffolding for converting REST APIs to GrAMPS data sources.

Thanks a million!

Ensure Node 8 compatibility

install.js doesn't work on Node 8.

Also, classes don't work without Babel tweaks.

Both of these issues should be fixed.

Support new description syntax

graphql 0.12 changed the description syntax from comments to string (blocks). The sample schema still uses the old description syntax.

GrAMPS CLI is intended for local development only.

I'm getting this error after running "yarn dev".

I followed all three steps below:

npx graphql-cli create -b gramps-graphql/data-source-base data-source-mydata

# 📂 move into the newly-created data source
cd $_

# 🚀 start the GraphQL Playground with your spankin’ new data source
yarn dev

I read somewhere that it might have to do with my NODE_ENV so I set it to "local", but that doesn't work either. Could anyone help me debug this? Thanks!

Yarn version: 1.3.2
Node version: 8.9.4

I'm following the Quick Guide here - part 1 (which is essentially the 3 commands above)

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.