Nathan Shively-Sanders 42a2d9e568 Excess property understands conditional types (#25584) ... Previously it did not, causing misleading excess property errors. Note that assignability errors with conditional types are still usually confusing. This PR doesn't address that. Also, make sure that exact matches in getSpellingSuggestion are skipped.		2018-07-11 11:24:40 -07:00
..
any
asyncGenerators
conditional	Excess property understands conditional types (#25584)	2018-07-11 11:24:40 -07:00
contextualTypes
forAwait
import	Module or import types (#22592)	2018-04-02 10:18:23 -07:00
intersection	Add tests	2018-04-27 16:50:09 -07:00
keyof	Add regression test	2018-06-03 11:59:24 -07:00
literal	Add tests	2018-05-21 16:43:55 -07:00
localTypes
mapped	Add tests	2018-02-13 06:48:03 -08:00
members	Revert more baselines, add jake task for typemock	2017-12-19 13:40:32 -08:00
namedTypes
never	Merge branch 'master' into vfs	2018-04-17 14:39:20 -07:00
nonPrimitive	Check that test cases produce expected types	2018-05-01 13:05:49 -07:00
objectTypeLiteral
primitives
rest	Add tests	2018-07-02 17:50:42 -10:00
specifyingTypes
spread	Unpatch vfs resolver and default lib rename	2018-05-03 14:18:50 -07:00
stringLiteral
thisType	disallow static field access	2018-06-05 18:42:21 +08:00
tuple	Add tests	2018-06-25 10:45:38 -10:00
typeAliases
typeParameters
typeRelationships	Combine keyof T inferences (#22525)	2018-03-19 16:56:51 -07:00
union	Index signatures contribute properties to unions (#25307)	2018-07-06 10:46:05 -07:00
uniqueSymbol	Fix initializer assignability for unique symbol	2018-02-02 13:13:21 -08:00
unknown	Update tests	2018-05-29 17:55:57 -07:00
witness