Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SIEM] GraphQL type generation fails to generate types #46754

Closed
spong opened this issue Sep 27, 2019 · 1 comment · Fixed by #47638
Closed

[SIEM] GraphQL type generation fails to generate types #46754

spong opened this issue Sep 27, 2019 · 1 comment · Fixed by #47638
Assignees
Labels
bug Fixes for quality problems that affect the customer experience chore Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM

Comments

@spong
Copy link
Member

spong commented Sep 27, 2019

With the latest from master, running node scripts/generate_types_from_graphql.js from ${KIBANA_HOME}/x-pack/legacy/plugins/siem to generate the graphql types fails with the following error:

  ✖ Parse configuration
    → Cannot convert undefined or null to object
    Generate outputs
Cannot convert undefined or null to object
(node:31823) UnhandledPromiseRejectionWarning: TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at normalize (/Users/garrettspong/dev/kibana/node_modules/graphql-code-generator/src/codegen.ts:84:33)
    at Task.task (/Users/garrettspong/dev/kibana/node_modules/graphql-code-generator/src/codegen.ts:150:17)
    at Promise.resolve.then.then.skipped (/Users/garrettspong/dev/kibana/node_modules/graphql-code-generator/node_modules/listr/lib/task.js:167:30)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
(node:31823) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:31823) [DEP0018] Depre

This appears to the be results of the recent upgrade of graphql-code-generator from "^0.13.0" to "^0.18.2", which introduces a familiar breaking change from a few months ago. Yay semver!

@spong spong added bug Fixes for quality problems that affect the customer experience chore Team:SIEM labels Sep 27, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience chore Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants