Skip to content

Conversation

ajafff and others added 30 commits July 8, 2018 21:25
When running with -w, do an initial compilation
* Explicitly typed js assignments: context sensitive

Explicitly typed special assignments should be context sensitive if they
have an explicit type tag. Previously no special assignments were
context sensitive because they are declarations, and in the common,
untyped, case we inspect the right side of the assignment to get the
type of the left side, and inspect the right side of the assignment to
get the type of the left side, etc etc.

Note that some special assignments still return `any` from
checkExpression, so still don't get the right type.

Fixes #25571

* Change prototype property handling+update bselines

* Fix indentation in test

* Update baselines
#25598)

* Don't report unused diagnostics when the unused node has a parse error

* Update test
* getContainingList: Handle TypeAliasDeclaration

* Handle ClassExpression and InterfaceDeclaration
Fix incorrect handling of preserveWatchOutput flag is in config file
Support resolveJsonModule option when files contain the json file
getLeftmostExpression: handle TaggedTemplateExpression
* Explicitly typed prototype assignments:ctx sensitive

Follow up to #25619: Add the necessary code to type `prototype`
correctly in prototype assignments so that code like
`F.prototype = { ... }` properly makes the object literal context
sensitive.

* Fix lint
Change jsDocTagNames to lower case.
Make 'pop' the first method that uses 'T' in 'Array'
…hildren

navigationBar: Don't merge unrelated grandchildren
…ial-assignments

Revert explicitly typed special assignments
@mhegazy mhegazy merged commit d71415a into release-3.0 Jul 16, 2018
@mhegazy mhegazy deleted the mergeMaster-7-16 branch July 16, 2018 20:43
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
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.

8 participants