Skip to content
This repository has been archived by the owner on May 17, 2024. It is now read-only.

Improving error messages #24

Merged
merged 1 commit into from
Jul 20, 2017
Merged

Conversation

BrunoBernardino
Copy link
Contributor

Specifically when a field has an empty array in .children and other kinds of invalid values, showing which field with </FieldSchema>,</FunctionSchema> instead of "anything" in [subschema 0],</FunctionSchema>.

Fixes #22

Specifically when a field has an empty array in .children and other kinds of invalid values, showing which field with `</FieldSchema>,</FunctionSchema>` instead of "anything" in `[subschema 0],</FunctionSchema>`.
@BrunoBernardino BrunoBernardino self-assigned this Jul 17, 2017
@kola-er
Copy link
Contributor

kola-er commented Jul 18, 2017

Seen, will review soon.

Copy link
Contributor

@kola-er kola-er left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It fixes the issue of inappropriate error message for the edge case of empty children list.

// results.errors[0].stack.should.eql('instance.operation.inputFields[0].default does not meet minimum length of 1');
results.errors[0].stack.should.eql('instance.operation.inputFields[0] is not exactly one from </FieldSchema>,</FunctionSchema>');
});

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improving the test coverage.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants