profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/IvanGoncharov/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Ivan Goncharov IvanGoncharov APIs.guru Lviv, Ukraine https://APIs.guru Maintainer of graphql-js. Need help with GraphQL I'm available for hire!

graphql/graphql-spec 13286

GraphQL is a query language and execution engine tied to any backend service.

graphql/graphiql 12087

GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.

graphql/graphql-playground 7173

🎮 GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration)

APIs-guru/graphql-voyager 6031

🛰️ Represent any GraphQL API as an interactive graph

graphql/express-graphql 5909

Create a GraphQL HTTP server with Express.

APIs-guru/graphql-apis 3151

📜 A collective list of public GraphQL APIs

graphql/swapi-graphql 934

A GraphQL schema and server wrapping SWAPI.

DataFire/DataFire 500

A framework for building integrations and APIs

graphql/graphql-wg 302

Working group notes for GraphQL

graphql/codemirror-graphql 147

GraphQL mode and helpers for CodeMirror.

pull request commentgraphql/swapi-graphql

Bump handlebars from 4.7.6 to 4.7.7

<a href="https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/12261526/40998988/199/#/?version=2"><img src="https://s3.amazonaws.com/cla-project-logo-prod/cla-not-signed.svg" alt="CLA Not Signed" align="left" height="28" width="328" ></a><br/><br /><ul><li><a href='https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/12261526/40998988/199/#/?version=2' target='_blank'>:x:</a> - dependabot[bot] The commit (6e9cfd040ce34361bd946b753019f822a9c373c6) is not authorized under a signed CLA. <a href='https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/12261526/40998988/199/#/?version=2' target='_blank'>Please click here to be authorized</a>. For further assistance with EasyCLA, <a href='https://jira.linuxfoundation.org/servicedesk/customer/portal/4' target='_blank'>please submit a support request ticket</a>.</li></ul>

dependabot[bot]

comment created time in 41 minutes

create barnchgraphql/swapi-graphql

branch : dependabot/npm_and_yarn/handlebars-4.7.7

created branch time in 41 minutes

PR opened graphql/swapi-graphql

Bump handlebars from 4.7.6 to 4.7.7

Bumps handlebars from 4.7.6 to 4.7.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.7 - February 15th, 2021</h2> <ul> <li>fix weird error in integration tests - eb860c0</li> <li>fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - b6d3de7</li> <li>fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - f058970</li> <li>refactor: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>) - 77825f8</li> <li>chore: start testing on Node.js 12 and 13 - 3789a30</li> </ul> <p>(POSSIBLY) BREAKING CHANGES:</p> <ul> <li>the changes from version <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md#v460---january-8th-2020">4.6.0</a> now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1633">#1633</a> for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.</li> </ul> <p>That is why we only bump the patch version despite mentioning breaking changes.</p> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">Commits</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/a9a8e403213583ca90cb7c872d3a22796c37d961"><code>a9a8e40</code></a> v4.7.7</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e66aed5b99c1b6c93564f37d627e34e5d60eb76e"><code>e66aed5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/7d4d170ce46a53084a41920c5c7387c131357989"><code>7d4d170</code></a> disable IE in Saucelabs tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/eb860c08998f8f506360d305d89e1f4b40f72a0a"><code>eb860c0</code></a> fix weird error in integration tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8"><code>b6d3de7</code></a> fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427"><code>f058970</code></a> fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/77825f8d3522356feb8e4160fac16344104d192b"><code>77825f8</code></a> refator: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3789a309554fd600caeae442f40881cf93eb3b54"><code>3789a30</code></a> chore: start testing on Node.js 12 and 13</li> <li>See full diff in <a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

pr created time in 41 minutes

pull request commentgraphql/dataloader

Bump handlebars from 4.5.1 to 4.7.7

<a href="https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/12261526/42237038/267/#/?version=2"><img src="https://s3.amazonaws.com/cla-project-logo-prod/cla-not-signed.svg" alt="CLA Not Signed" align="left" height="28" width="328" ></a><br/><br /><ul><li><a href='https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/12261526/42237038/267/#/?version=2' target='_blank'>:x:</a> - dependabot[bot] The commit (35364579fb501969092c2b52ac37c695ff945307) is not authorized under a signed CLA. <a href='https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/12261526/42237038/267/#/?version=2' target='_blank'>Please click here to be authorized</a>. For further assistance with EasyCLA, <a href='https://jira.linuxfoundation.org/servicedesk/customer/portal/4' target='_blank'>please submit a support request ticket</a>.</li></ul>

dependabot[bot]

comment created time in an hour

delete branch graphql/dataloader

delete branch : dependabot/npm_and_yarn/handlebars-4.7.6

delete time in an hour

PR closed graphql/dataloader

Bump handlebars from 4.5.1 to 4.7.6 dependencies

Bumps handlebars from 4.5.1 to 4.7.6. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.6 - April 3rd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1672">#1672</a> - Switch cmd parser to latest minimist (<a href="https://api.github.com/users/dougwilson">@dougwilson</a></li> </ul> <p>Compatibility notes:</p> <ul> <li>Restored Node.js compatibility</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.5...v4.7.6">Commits</a></p> <h2>v4.7.5 - April 2nd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><del>Node.js version support has been changed to v6+</del> Reverted in 4.7.6</li> </ul> <p>Compatibility notes:</p> <ul> <li><del>Node.js < v6 is no longer supported</del> Reverted in 4.7.6</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.4...v4.7.5">Commits</a></p> <h2>v4.7.4 - April 1st, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1666">#1666</a> - Replaced minimist with yargs for handlebars CLI (<a href="https://api.github.com/users/aorinevo">@aorinevo</a>, <a href="https://api.github.com/users/AviVahl">@AviVahl</a> & <a href="https://api.github.com/users/fabb">@fabb</a>)</li> </ul> <p>Compatibility notes:</p> <ul> <li>No incompatibilities are to be expected</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.3...v4.7.4">Commits</a></p> <h2>v4.7.3 - February 5th, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1644">#1644</a> - Download links to aws broken on handlebarsjs.com - access denied (<a href="https://api.github.com/users/Tea56">@Tea56</a>)</li> <li>Fix spelling and punctuation in changelog - d78cc73</li> </ul> <p>Bugfixes:</p> <ul> <li>Add Type Definition for Handlebars.VERSION, Fixes <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1647">#1647</a> - 4de51fe</li> <li>Include Type Definition for runtime.js in Package - a32d05f</li> </ul> <p>Compatibility notes:</p> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e6ad93ea01bcde1f8ddaa4b4ebe572dd616abfaa"><code>e6ad93e</code></a> v4.7.6</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/2bf4fc6fd3ae3d8f076d628653f284d85faebeb4"><code>2bf4fc6</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b64202bc9197307bd785a58693e3820eb9bb41a8"><code>b64202b</code></a> Update release-notes.md</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/c2f1e6203178918569f085e12afdb762cae17fb0"><code>c2f1e62</code></a> Switch cmd parser to latest minimist</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/08e9a11a34c3ad8387a0b85b1334f97cab85191a"><code>08e9a11</code></a> Revert "chore: set Node.js compatibility to v6+"</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/1fd2edee2a12fb228061fcde807905c6b14339c4"><code>1fd2ede</code></a> v4.7.5</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3c9c2f5cf29cf10f54d5fe4daca6b24b65f0adcf"><code>3c9c2f5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/16487a088e13f4d52c6fd6610b9ec71c4a51be8a"><code>16487a0</code></a> chore: downgrade yargs to v14</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/309d2b49a11628d2a8f052c5587e7459968cd705"><code>309d2b4</code></a> chore: set Node.js compatibility to v6+</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/645ac73844918668f9a2f41e49b7cb18ce5abf36"><code>645ac73</code></a> test: fix integration tests</li> <li>Additional commits viewable in <a href="https://github.com/wycats/handlebars.js/compare/v4.5.1...v4.7.6">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~erisds">erisds</a>, a new releaser for handlebars since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+20 -35

1 comment

1 changed file

dependabot[bot]

pr closed time in an hour

pull request commentgraphql/dataloader

Bump handlebars from 4.5.1 to 4.7.6

Superseded by #267.

dependabot[bot]

comment created time in an hour

create barnchgraphql/dataloader

branch : dependabot/npm_and_yarn/handlebars-4.7.7

created branch time in an hour

PR opened graphql/dataloader

Bump handlebars from 4.5.1 to 4.7.7

Bumps handlebars from 4.5.1 to 4.7.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.7 - February 15th, 2021</h2> <ul> <li>fix weird error in integration tests - eb860c0</li> <li>fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - b6d3de7</li> <li>fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - f058970</li> <li>refactor: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>) - 77825f8</li> <li>chore: start testing on Node.js 12 and 13 - 3789a30</li> </ul> <p>(POSSIBLY) BREAKING CHANGES:</p> <ul> <li>the changes from version <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md#v460---january-8th-2020">4.6.0</a> now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1633">#1633</a> for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.</li> </ul> <p>That is why we only bump the patch version despite mentioning breaking changes.</p> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">Commits</a></p> <h2>v4.7.6 - April 3rd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1672">#1672</a> - Switch cmd parser to latest minimist (<a href="https://api.github.com/users/dougwilson"><code>@​dougwilson</code></a></li> </ul> <p>Compatibility notes:</p> <ul> <li>Restored Node.js compatibility</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.5...v4.7.6">Commits</a></p> <h2>v4.7.5 - April 2nd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><del>Node.js version support has been changed to v6+</del> Reverted in 4.7.6</li> </ul> <p>Compatibility notes:</p> <ul> <li><del>Node.js < v6 is no longer supported</del> Reverted in 4.7.6</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.4...v4.7.5">Commits</a></p> <h2>v4.7.4 - April 1st, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1666">#1666</a> - Replaced minimist with yargs for handlebars CLI (<a href="https://api.github.com/users/aorinevo"><code>@​aorinevo</code></a>, <a href="https://api.github.com/users/AviVahl"><code>@​AviVahl</code></a> & <a href="https://api.github.com/users/fabb"><code>@​fabb</code></a>)</li> </ul> <p>Compatibility notes:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/a9a8e403213583ca90cb7c872d3a22796c37d961"><code>a9a8e40</code></a> v4.7.7</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e66aed5b99c1b6c93564f37d627e34e5d60eb76e"><code>e66aed5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/7d4d170ce46a53084a41920c5c7387c131357989"><code>7d4d170</code></a> disable IE in Saucelabs tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/eb860c08998f8f506360d305d89e1f4b40f72a0a"><code>eb860c0</code></a> fix weird error in integration tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8"><code>b6d3de7</code></a> fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427"><code>f058970</code></a> fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/77825f8d3522356feb8e4160fac16344104d192b"><code>77825f8</code></a> refator: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3789a309554fd600caeae442f40881cf93eb3b54"><code>3789a30</code></a> chore: start testing on Node.js 12 and 13</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e6ad93ea01bcde1f8ddaa4b4ebe572dd616abfaa"><code>e6ad93e</code></a> v4.7.6</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/2bf4fc6fd3ae3d8f076d628653f284d85faebeb4"><code>2bf4fc6</code></a> Update release notes</li> <li>Additional commits viewable in <a href="https://github.com/wycats/handlebars.js/compare/v4.5.1...v4.7.7">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+20 -35

0 comment

1 changed file

pr created time in an hour

issue commentgraphql/graphql-spec

Explicitly state in spec that full introspection output is equivalent to full SDL document

hence they are simply NOT directives

This is a subjective judgment that is based on a personal understanding of what the directive represents. I understand your point of view. Probably the best that I can advise in this situation is to relate to introspection as a single source of truth. SDL (for the client, let's call it "public") is based on introspection. Yes, you can say that they are identical. However, the server can use (to be built) to a slightly different SDL. And these differences seem to be reduced only to directives. Not too big problem I think. I repeat - introspection is first, and SDL is only a derivative "beautiful" form of notation. You do not know how the server is built. It does not matter completely if it is built on the basis of a some SDL document, code first, schema stored in some relational database or in any other way, even at quantum nanoparticles.

rivantsov

comment created time in 4 hours

issue commentgraphql/graphiql

graphql-language-service-interface Module parse failed: Unexpected token (132:19)

It seems the language service has started using the ? operator which seems to cause issues (foo?.bar)

I was able to resolve this by rolling back to older working versions:

"graphiql": "^0.14.2",
"graphql": "^14.5.8",
"graphql-language-service-interface": "2.1.0",

Regards, Paul

ptallett

comment created time in 5 hours

Pull request review commentgraphql/graphql-js

RFC: Default value validation & coercion

 export function isRequiredInputField( }  export type GraphQLInputFieldMap = ObjMap<GraphQLInputField>;++/**+ * Historically GraphQL.js allowed default values to be provided as+ * assumed-coerced "internal" values, however default values should be provided+ * as "external" pre-coerced values. `uncoerceDefaultValue()` will convert such+ * "internal" values to "external" values to avoid breaking existing clients.+ *+ * This performs the opposite of `coerceInputValue()`. Given an "internal"+ * coerced value, reverse the process to provide an "external" uncoerced value.+ *+ * This function should not throw Errors on incorrectly shaped input. Instead+ * it will simply pass through such values directly.+ *+ */+function uncoerceDefaultValue(value: mixed, type: GraphQLInputType): mixed {+  // Explicitly return the value null.+  if (value === null) {+    return null;+  }++  // Unwrap type+  const namedType = getNamedType(type);++  if (isIterableObject(value)) {+    return Array.from(value, (itemValue) =>+      uncoerceDefaultValue(itemValue, namedType),+    );+  }++  if (isInputObjectType(namedType)) {+    if (!isObjectLike(value)) {+      return value;+    }++    const fieldDefs = namedType.getFields();+    return mapValue(value, (fieldValue, fieldName) =>+      fieldName in fieldDefs+        ? uncoerceDefaultValue(fieldValue, fieldDefs[fieldName].type)+        : fieldValue,+    );+  }++  if (isLeafType(namedType)) {+    try {+      // For leaf types (Scalars, Enums), serialize is the oppose of coercion+      // (parseValue) and will produce an "external" value.+      return namedType.serialize(value);

I think option 1 is best and imho that it is very important to fix the reference implementation to reflect the spec properly.

Thanks for your additional comments above, much appreciated.

leebyron

comment created time in 8 hours

pull request commentardatan/graphql-tools

chore(deps): update dependency graphql-upload to v12

The latest changes of this PR are available as alpha in npm (based on the declared changesets):


renovate[bot]

comment created time in 9 hours

pull request commentardatan/graphql-tools

chore(deps): update dependency graphql-upload to v12

⚠️ No Changeset found

Latest commit: 133b3180521a9a61deae1797747c92a80da1efd6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

<details><summary>This PR includes no changesets</summary>

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

</details>

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

renovate[bot]

comment created time in 9 hours

create barnchardatan/graphql-tools

branch : renovate/graphql-upload-12.x

created branch time in 9 hours

PR opened ardatan/graphql-tools

chore(deps): update dependency graphql-upload to v12

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-upload 11.0.0 -> 12.0.0 age adoption passing confidence

Release Notes

<details> <summary>jaydenseric/graphql-upload</summary>

v12.0.0

Compare Source

Major
  • Updated Node.js support to ^12.20 || >= 14.13.
  • Updated dev dependencies, some of which require newer Node.js versions than previously supported.
  • The tests are now ESM in .mjs files instead of CJS in .js files.
  • Replaced the the package.json exports field public subpath folder mapping (deprecated by Node.js) with a subpath pattern. Deep require paths must now include the .js file extension.
Minor
  • Added a package sideEffects field.
Patch
  • Updated dependencies.
  • Lint fixes for the updated Prettier version.
  • Updated GitHub Actions CI config:
    • Updated the tested Node.js versions to v12, v14, v16.
    • Updated actions/checkout to v2.
    • Updated actions/setup-node to v2.
    • Simplify config with the npm install-test command.
    • Don’t specify the CI environment variable as it’s set by default.
  • Removed npm-debug.log from the .gitignore file as npm v4.2.0+ doesn’t create it in the current working directory.
  • Updated the EditorConfig URL.
  • Updated the package keywords field.
  • More specific package main field path.
  • Simplified JSDoc related package scripts now that jsdoc-md v10 automatically generates a Prettier formatted readme.
  • Added a package test:jsdoc script that checks the readme API docs are up to date with the source JSDoc.
  • Refactored private constants from exports of a single module to individual modules.
  • Fixed test name and comment typos.
  • Updated external URLs in docs.
  • Prettier format for a JSDoc code example.
  • Updated a GraphQLUpload code example to use @graphql-tools/schema instead of graphql-tools.
  • Removed from the readme the notice that the package was previously published as apollo-upload-server.
  • Simplified the readme “Setup” and “Support” sections.

</details>


Configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+12 -12

0 comment

3 changed files

pr created time in 9 hours

Pull request review commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

+import { inspect } from '../jsutils/inspect';+import { isIterableObject } from '../jsutils/isIterableObject';++import type { ConstValueNode } from '../language/ast';+import { Kind } from '../language/kinds';++import type { GraphQLInputType } from '../type/definition';+import {+  getNamedType,+  isLeafType,+  isInputObjectType,+} from '../type/definition';++/**+ * Produces a GraphQL Value AST given a JavaScript value.+ *+ * A GraphQL type may be provided, which will be used to interpret different+ * JavaScript values if it defines a `valueToLiteral` method.+ *+ * | JavaScript Value  | GraphQL Value        |+ * | ----------------- | -------------------- |+ * | Object            | Input Object         |+ * | Array             | List                 |+ * | Boolean           | Boolean              |+ * | String            | String               |+ * | Number            | Int / Float          |+ * | null / undefined  | Null                 |+ *+ * Note: This function does not perform any type validation or coercion.+ */+export function valueToLiteral(+  value: mixed,+  type?: GraphQLInputType,+): ConstValueNode {+  // Like JSON, a null literal is produced for null and undefined.+  if (value == null) {+    return { kind: Kind.NULL };+  }++  const namedType = type && getNamedType(type);++  // Convert JavaScript array to GraphQL list.+  if (isIterableObject(value)) {+    return {+      kind: Kind.LIST,+      values: Array.from(value, (item) => valueToLiteral(item, namedType)),+    };+  }++  // Does this type (if provided) define `valueToLiteral` which returns a value?

what about input object types? Does InputObject define a valueToLiteral? It either should or we should define the appropriate logic here.

leebyron

comment created time in 11 hours

Pull request review commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

+import { inspect } from '../jsutils/inspect';+import { isIterableObject } from '../jsutils/isIterableObject';++import type { ConstValueNode } from '../language/ast';+import { Kind } from '../language/kinds';++import type { GraphQLInputType } from '../type/definition';+import {+  getNamedType,+  isLeafType,+  isInputObjectType,+} from '../type/definition';++/**+ * Produces a GraphQL Value AST given a JavaScript value.+ *+ * A GraphQL type may be provided, which will be used to interpret different+ * JavaScript values if it defines a `valueToLiteral` method.+ *+ * | JavaScript Value  | GraphQL Value        |+ * | ----------------- | -------------------- |+ * | Object            | Input Object         |+ * | Array             | List                 |+ * | Boolean           | Boolean              |+ * | String            | String               |+ * | Number            | Int / Float          |+ * | null / undefined  | Null                 |+ *+ * Note: This function does not perform any type validation or coercion.+ */+export function valueToLiteral(+  value: mixed,+  type?: GraphQLInputType,+): ConstValueNode {+  // Like JSON, a null literal is produced for null and undefined.+  if (value == null) {+    return { kind: Kind.NULL };+  }++  const namedType = type && getNamedType(type);++  // Convert JavaScript array to GraphQL list.+  if (isIterableObject(value)) {+    return {+      kind: Kind.LIST,+      values: Array.from(value, (item) => valueToLiteral(item, namedType)),+    };+  }++  // Does this type (if provided) define `valueToLiteral` which returns a value?+  if (isLeafType(namedType) && namedType.valueToLiteral != null) {+    const literal = namedType.valueToLiteral(value);+    if (literal) {+      return literal;+    }+  }++  // Otherwise, perform a JS-to-Literal default equivalency.

we should make clear that this is deprecated, possibility wrong behaviour and Scalars should define their appropriate logic.

leebyron

comment created time in 11 hours

pull request commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

I want to state that I think getting rid of variable references inside complex ast literal is the right way to preserve the current behaviour while making custom scalar implementations easier and more robust. Great work @leebyron

leebyron

comment created time in 11 hours

issue commentgraphql/graphql-spec

Explicitly state in spec that full introspection output is equivalent to full SDL document

@benjie -

They’re useful for schema first development; they do not appear/exist publicly.

wow... so it is dev artefact. i mean really, WOW... server dev artifacts, not public protocol... admittedly, things are not as I imagined... I stupidly based all on the first sentence of the Overview section:

GraphQL is a query language designed to build client applications by providing an intuitive and flexible syntax and system for describing their data requirements and interactions.

client... but instead it is a description of server dev artifacts... You see the problem? I kinda do. I have to think a bit and probably come up with RFC draft that discusses this and the other equivalency problem.

About publishing schema doc thru endpoint - yes, I kinda over-estimated how 'common' is this practice, just looked at couple of APIs (Github, Paypal etc). Ok, my bad. About GraphQL over Http - I did not mean it is there, I meant if "schema doc endpoint spec" should be placed somewhere, it should be in this other http spec.

Ivan: ... is not true. - yah, I know it is not true, my point is that it should be true. And what you describe as build time directives and introspectability... again, these are dev artifacts, they should not be concern of the spec IMHO, hence they are simply NOT directives - you just used the same thing to define real dirs (Attributes?) and "build time" dirs, and suppress the latter by this flag - which means then are not dirs actually

thanks guys.. let me think about this and next steps. literally need to recover from the "surprise"

rivantsov

comment created time in 11 hours

Pull request review commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

 export function valueFromAST(    // istanbul ignore else (See: 'https://github.com/graphql/graphql-js/issues/2618')   if (isLeafType(type)) {+    const constValueNode = replaceASTVariables(valueNode, variables);+     // Scalars and Enums fulfill parsing a literal value via parseLiteral().     // Invalid values represent a failure to parse correctly, in which case     // no value is returned.     let result;     try {-      result = type.parseLiteral(valueNode, variables);+      result = type.parseLiteral

how do I need to read this? if we have an existing parseLiteral we use it? I would expect that it would be: if we have a literalToValue we use it, otherwise we fall back

leebyron

comment created time in 11 hours

Pull request review commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

+import type { ObjMap } from '../jsutils/ObjMap';++import type { ValueNode, ConstValueNode } from '../language/ast';+import { Kind } from '../language/kinds';+import { visit } from '../language/visitor';++import { valueToLiteral } from './valueToLiteral';++/**+ * Replaces any Variables found within an AST Value literal with literals+ * supplied from a map of variable values, returning a constant value.+ *+ * Used primarily to ensure only complete constant values are used during input+ * coercion of custom scalars which accept complex literals.+ */+export function replaceASTVariables(+  valueNode: ValueNode,+  variables: ?ObjMap<mixed>,+): ConstValueNode {+  return visit(valueNode, {+    Variable(node) {+      return valueToLiteral(variables?.[node.name.value]);

we need to consider non provided variables values: a variables reference ast reference would need to completely removed I think to emulate a non existing value (and not just null)

leebyron

comment created time in 11 hours

PR opened APIs-guru/asyncapi-directory

Bump handlebars from 4.7.3 to 4.7.7

Bumps handlebars from 4.7.3 to 4.7.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md">handlebars's changelog</a>.</em></p> <blockquote> <h2>v4.7.7 - February 15th, 2021</h2> <ul> <li>fix weird error in integration tests - eb860c0</li> <li>fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - b6d3de7</li> <li>fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>) - f058970</li> <li>refactor: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>) - 77825f8</li> <li>chore: start testing on Node.js 12 and 13 - 3789a30</li> </ul> <p>(POSSIBLY) BREAKING CHANGES:</p> <ul> <li>the changes from version <a href="https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md#v460---january-8th-2020">4.6.0</a> now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See <a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1633">#1633</a> for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.</li> </ul> <p>That is why we only bump the patch version despite mentioning breaking changes.</p> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.6...v4.7.7">Commits</a></p> <h2>v4.7.6 - April 3rd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1672">#1672</a> - Switch cmd parser to latest minimist (<a href="https://api.github.com/users/dougwilson"><code>@​dougwilson</code></a></li> </ul> <p>Compatibility notes:</p> <ul> <li>Restored Node.js compatibility</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.5...v4.7.6">Commits</a></p> <h2>v4.7.5 - April 2nd, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><del>Node.js version support has been changed to v6+</del> Reverted in 4.7.6</li> </ul> <p>Compatibility notes:</p> <ul> <li><del>Node.js < v6 is no longer supported</del> Reverted in 4.7.6</li> </ul> <p><a href="https://github.com/wycats/handlebars.js/compare/v4.7.4...v4.7.5">Commits</a></p> <h2>v4.7.4 - April 1st, 2020</h2> <p>Chore/Housekeeping:</p> <ul> <li><a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1666">#1666</a> - Replaced minimist with yargs for handlebars CLI (<a href="https://api.github.com/users/aorinevo"><code>@​aorinevo</code></a>, <a href="https://api.github.com/users/AviVahl"><code>@​AviVahl</code></a> & <a href="https://api.github.com/users/fabb"><code>@​fabb</code></a>)</li> </ul> <p>Compatibility notes:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/a9a8e403213583ca90cb7c872d3a22796c37d961"><code>a9a8e40</code></a> v4.7.7</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e66aed5b99c1b6c93564f37d627e34e5d60eb76e"><code>e66aed5</code></a> Update release notes</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/7d4d170ce46a53084a41920c5c7387c131357989"><code>7d4d170</code></a> disable IE in Saucelabs tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/eb860c08998f8f506360d305d89e1f4b40f72a0a"><code>eb860c0</code></a> fix weird error in integration tests</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/b6d3de7123eebba603e321f04afdbae608e8fea8"><code>b6d3de7</code></a> fix: check prototype property access in strict-mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/f0589701698268578199be25285b2ebea1c1e427"><code>f058970</code></a> fix: escape property names in compat mode (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1736">#1736</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/77825f8d3522356feb8e4160fac16344104d192b"><code>77825f8</code></a> refator: In spec tests, use expectTemplate over equals and shouldThrow (<a href="https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1683">#1683</a>)</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/3789a309554fd600caeae442f40881cf93eb3b54"><code>3789a30</code></a> chore: start testing on Node.js 12 and 13</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/e6ad93ea01bcde1f8ddaa4b4ebe572dd616abfaa"><code>e6ad93e</code></a> v4.7.6</li> <li><a href="https://github.com/handlebars-lang/handlebars.js/commit/2bf4fc6fd3ae3d8f076d628653f284d85faebeb4"><code>2bf4fc6</code></a> Update release notes</li> <li>Additional commits viewable in <a href="https://github.com/wycats/handlebars.js/compare/v4.7.3...v4.7.7">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+19 -37

0 comment

1 changed file

pr created time in 12 hours

pull request commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

One important detail:

What should the formal relationship between valueToLiteral and literalToValue be?

For example for ID: This code does valueToLiteral(literalToValue(AstInt(123))) == AstInt(123) but also valueToLiteral(literalToValue(AstString("123"))) == AstInt(123)

This means valueToLiteral maps two different values to the same Literal (In math speak: it is not injective) and both functions are not the inverse to each other.

If we want to make both functions the inverse to each other we would require that different literals always produce different external input values and different external input values produce different literals. I don't think we can do that as this is a constraint we have not had so far and we would break existing code.

This probably means we require that for every valid literal x literalToValue(valueToLiteral(literalToValue(x))) is possible and for every valid input value y valueToLiteral(literalToValue(valueToLiteral(y))) is possible, but not more.

leebyron

comment created time in 12 hours

Pull request review commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

+import { Maybe } from '../jsutils/Maybe';+import { ObjMap } from '../jsutils/ObjMap';++import { ValueNode, ConstValueNode } from '../language/ast';++/**+ * Replaces any Variables found within an AST Value literal with literals+ * supplied from a map of variable values, returning a constant value.+ *+ * Used primarily to ensure only complete constant values are used during input+ * coercion of custom scalars which accept complex literals.+ */+export function replaceASTVariables(+  valueNode: ValueNode,+  variables: Maybe<ObjMap<unknown>>,

just to be clear here: these are the raw (uncoerced variables) right?

leebyron

comment created time in 13 hours

issue commentgraphql/express-graphql

Run Test on Node v12 Failed

@justinmchase thanks for that. I made various changes in the PR accordingly e.g. https://github.com/graphql/express-graphql/pull/755/files#diff-ca140513f036f6bfbb6a70f1aa37af734be5b256801097041211bd7fa7f15584R18 node12 tests still failed. Maybe I did something wrong?

junminstorage

comment created time in 13 hours

pull request commentgraphql/graphql-js

Add valueToLiteral() and literalToValue()

Yeah you've got this exactly right. What does it mean to have a variable within a leaf value? There is no way to represent that in the type system.

leebyron

comment created time in 13 hours

Pull request review commentgraphql/graphql-js

Refine parse and AST to represent ConstValue

 export type ListValueNode = {|   +values: $ReadOnlyArray<ValueNode>, |}; +export type ConstListValueNode = {|+  +kind: 'ListValue',

Another way to frame this is that a ConstValueNode is a ValueNode, it's a subset. So we wouldn't want to set anything on it, like a variation of kind or any other added data that would make a ConstValueNode not a subset of ValueNode

leebyron

comment created time in 13 hours

issue commentgraphql/graphiql

graphql-language-service-interface Module parse failed: Unexpected token (132:19)

Unfortunately, as I said, I don't have a webpack config as I am using Create React App.

ptallett

comment created time in 13 hours