-
Notifications
You must be signed in to change notification settings - Fork 86
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
Record Type allows non-defined keys #1046
Comments
It makes sense. Reporting unknown keys included in literals should help. |
Comment moved from #256
Ackchyually nonexistent key is distinguishable from # @type var x: { name: String, ?email: String? }
x = { name: "foo" } # OK 💯 P.S. see ruby/rbs#504 regarding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When defining a record type, I expected the type checker to complain if an additional (non-defined) key was supplied by the user. Specifically I expected the following to fail type checking:
Is my assumption wrong or is this a bug in Steep? Might it be related with the change in #256?
Version tested: 1.6.0
The text was updated successfully, but these errors were encountered: