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

Input & Output type definition #462

Merged
merged 1 commit into from
Jun 11, 2018
Merged

Input & Output type definition #462

merged 1 commit into from
Jun 11, 2018

Conversation

leebyron
Copy link
Collaborator

Throughtout the spec we refer to input and output types but never clearly define them in a referenced section. This adds that section and removes the ad-hoc descriptions from elsewhere in the spec.

It also uses the formal algorithms in place of prose where relevant.

Finally it adds to the schema validation rules for Object, Interface, and Input Object fields / arguments.

Fixes #447

Throughtout the spec we refer to input and output types but never clearly define them in a referenced section. This adds that section and removes the ad-hoc descriptions from elsewhere in the spec.

It also uses the formal algorithms in place of prose where relevant.

Finally it adds to the schema validation rules for Object, Interface, and Input Object fields / arguments.
@leebyron leebyron force-pushed the input-output-type branch from c02547c to a6535f3 Compare June 10, 2018 23:49
@leebyron leebyron merged commit 6ff258f into master Jun 11, 2018
@leebyron leebyron deleted the input-output-type branch June 11, 2018 00:03
@leebyron leebyron added the 🏁 Accepted (RFC 3) RFC Stage 3 (See CONTRIBUTING.md) label Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏁 Accepted (RFC 3) RFC Stage 3 (See CONTRIBUTING.md)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants