Skip to content

Conversation

sandersn
Copy link
Member

Fixes #5372.

When an object literal, for example, is returned that does not match the type of the consturctor, add detail about a field that is required but missing.

Do this by passing checkTypeAssignableTo node.expression instead of undefined -- the rest of
the error reporting infrastructure is already in place.

When an object literal, for example, is returned that does not match the
type of the consturctor, add detail about a field that is required but
missing.

Do this by passing `node.expression` instead of `undefined` -- the rest of
the error reporting infrastructure is already in place.
@mhegazy
Copy link
Contributor

mhegazy commented Oct 30, 2015

👍

sandersn added a commit that referenced this pull request Oct 30, 2015
…turn-error-message

Improve constructor object return error message
@sandersn sandersn merged commit 16f69da into master Oct 30, 2015
@sandersn sandersn deleted the improve-constructor-object-return-error-message branch October 30, 2015 17:17
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants