This repository was archived by the owner on Sep 2, 2020. It is now read-only.
Fixes #223 - handle case when .graphqlconfig defines projects #225
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In addition to fix the issue details in #223, this patch also addresses the errors we were seeing in the console this morning:
The above unhandled error was raised by invoking
Object.values(undefined)
inMessageProcessor.js
in the case where a.graphqlconfig
file defined project-level settings.