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

check lower bounds when verifying type compatibility #162

Closed

abstratt opened this issue Feb 16, 2019 · 0 comments

Labels

Owner

abstratt commented Feb 16, 2019

Should check lower bounds when verifying type compatibility. Need support for coercing optional values as required ones before we can do that.

abstratt added the enhancement label

abstratt added a commit that referenced this issue


          preparing to validating required vs. optional values #162

97c3447

abstratt added a commit that referenced this issue


          added test case for verifying required vs optional values #162

ba595d5

abstratt added a commit that referenced this issue


          showing type multiplicity in string representation #162

c3158ae

abstratt mentioned this issue

Consider making optional the new default #163

Open

abstratt closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment