Skip to content
This repository has been archived by the owner on Feb 4, 2019. It is now read-only.

Ways to detect and respond to invalid input types on Interfaces #11

Open
motns opened this issue Apr 4, 2013 · 0 comments
Open

Ways to detect and respond to invalid input types on Interfaces #11

motns opened this issue Apr 4, 2013 · 0 comments

Comments

@motns
Copy link
Owner

motns commented Apr 4, 2013

Currently we attempt type coersion and if it fails, we set the value to Nil (which is later used in validations). We should be able to signal to the client that the type of input data they provided was wrong to begin with.

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

No branches or pull requests

1 participant