TypeScript版本： 2.2.1 / nightly (2.2.0-dev.201xxxxx)

代码

以下是JavaScript代码：

/**
* @param {MessageActivity} activity
* @param {IConversationContext} context
*/
export function Prompt_beforeResponse(activity, context)
{
  // MessageActivity is defined in typescript definition provided to the editor as having 4 properties (attachements, text, speak, type). 
 // Typing activity. will show those for properties but also: 
 //     activity  - why should activity be under itself?
 //     context - why should the second parameter be under activity?
 //     IConversationContext - why would a type, that is not a property in any object be under activity?
 //     MessageActivity - same question as above
 //     onRun - why should a global function be under activity
 //     Prompt_when - same as above
 //     Prompt_beforeResponse - same question as above and this is the function itself

//  Here is another example. obj. should display only a and b, but it also shows activity, context, MessageActivity, IConversationContext, etc.
   /**
* @type {{a: number, b: string }}
*/
   var obj = {};
   obj.
}

// A *self-contained* demonstration of the problem follows...

预期行为：

当一个JavaScript类型不是"any"时，即在jsdoc中或在typescript定义助手中定义时(参见https://github.com/Microsoft/TypeScript/wiki/JavaScript-Language-Service-in-Visual-Studio#unsupported-patterns),只有那些已定义的成员应该成为intellisense的一部分。
即使类型是any,像那样在intellisense上抛出所有内容也破坏了找出对象下合理内容的目的。

实际行为：

在intellisense中出现了一堆毫无意义的额外条目，无论是类型化的还是未类型化的场景，但这对于类型化场景特别糟糕，因为在那里已经投入了一些心思来确定应该出现在intellisense中的内容。添加所有这些条目使得intellisense功能变得不那么有用。