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.

Sign up for GitHub

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

Jump to bottom

GraphQLBridge mishandles initialValue. #183

Closed
yourse1f-yourorg opened this issue Feb 5, 2017 · 1 comment
Closed

GraphQLBridge mishandles initialValue. #183

yourse1f-yourorg opened this issue Feb 5, 2017 · 1 comment
Assignees
@radekmie
Labels
Type: Feature New features and feature requests

Comments

@yourse1f-yourorg
Copy link

Array and Object initial values are suppressed. I don't know if that's correct.

Primitive initial values should be passed through to set field initial values, but undefined is returned.
martinhbramwell pushed a commit to warehouseman/uniforms that referenced this issue Feb 5, 2017
@dude-awap
GraphQLBridge handles primitive initial values correctly (closes vazc…
d082b9c 
…o#183).

Unit tests upgraded to respect new behaviour.
@radekmie radekmie self-assigned this Feb 5, 2017
@radekmie radekmie added the Type: Feature New features and feature requests label Feb 5, 2017
@radekmie
Copy link
Contributor

radekmie commented Feb 5, 2017

These are not being suppressed, but not handled at all.

@radekmie radekmie moved this to Closed in Open Source Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@radekmie radekmie

Labels
Type: Feature New features and feature requests
Projects
Open Source
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@radekmie @yourse1f-yourorg