- 25 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 20 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 26 1月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 16 1月, 2016 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 11 12月, 2015 1 次提交
-
-
由 Jason Malinowski 提交于
-
- 21 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 20 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 10 10月, 2015 1 次提交
-
-
由 Tanner Gooding 提交于
-
- 21 4月, 2015 1 次提交
-
-
由 David Poeschl 提交于
- Fixes #496, an error when finding reference on namespaces defined in metadata - Groups all namespace definitions & references under a single node, which itself is non-navigable. Prior to this change, there would be lots of top-level nodes for the same namespace with 0 references.
-
- 21 3月, 2015 2 次提交
-
-
由 beep boop 提交于
Now that the comment formatting issue is fixed in the Formatter type, we can run the formatter on the remainder of the VB code base. closes #1424
-
由 David Poeschl 提交于
These tests were broken in #1396, and this is a test-only fix.
-
- 20 3月, 2015 1 次提交
-
-
由 David Poeschl 提交于
Fixes internal issue #1138943. In the SymbolFinder API, references to constructors are included as references to both the constructor method symbol and the related type symbol. Because reference locations are deduplicated across all results shown in Find References, we have to decide which definition node to use as the parent. Prior to this change the first related definition returned to us by the SymbolFinder won, but this ordering was not guaranteed to be consistent. This change introduces a precedence ordering for definitions returned by the SymbolFinder that currently guarantees that members will be preferred over types. Additionally, this change removes the requirement that definitions shown in Find References have distinct locations. This allows us to meaningfully separate references between a type and its default constructor which has the same location.
-