- 27 2月, 2016 3 次提交
-
-
由 Brett V. Forsgren 提交于
-
由 Brett V. Forsgren 提交于
Due to issues #7584 and #7587 adding `this.`/`Me.` is disabled for methods and events. Also add tests for verifying that no diagnostics are generated for static access or `base`/`MyBase` access.
-
由 Brett V. Forsgren 提交于
-
- 26 2月, 2016 5 次提交
-
-
由 Heejae Chang 提交于
Get support for squiggles and LB in "AnyCode" workspace
-
由 Heejae Chang 提交于
disable entry filter definition for now.
-
由 Heejae Chang 提交于
the base type we need to use EntryFilterDefinition is exchange type that needs to be moved to immutable dll. for more detail see https://github.com/dotnet/roslyn/issues/9096
-
由 Huizhong Long 提交于
-
由 Artur Spychaj 提交于
Merge master into future
-
- 25 2月, 2016 5 次提交
-
-
由 Balaji Krishnan 提交于
Feature: Suggest implicit or explicit typing code styles.
-
由 Balaji Krishnan 提交于
.. symbol than Parsing the display string of the symbol.
-
由 Balaji Krishnan 提交于
being a denylist to being an acceptlist.
-
由 Balaji Krishnan 提交于
minor naming changes and moving some code around.
-
由 Balaji Krishnan 提交于
Most fixes are about code style. Major changes are in: 1. the algorithm to determine if type is apparent in creation or conversion methods. 2. option serialization/deserialization.
-
- 24 2月, 2016 26 次提交
-
-
由 Balaji Krishnan 提交于
-
由 Huizhong Long 提交于
-
由 Huizhong Long 提交于
-
由 Huizhong Long 提交于
-
由 Balaji Krishnan 提交于
-
由 Balaji Krishnan 提交于
I'd overlooked the fact that !isChecked enforces `use explicit type` and hadn't stored enforcement level values then. This fixes the bug.
-
由 Balaji Krishnan 提交于
-
由 Balaji Krishnan 提交于
... with notification levels and also test notification levels.
-
由 Balaji Krishnan 提交于
If notification option is set to none, do not show a diagnostic.
-
由 Balaji Krishnan 提交于
.. and push common code down into Abstract base class. CheckBox ViewModel and CheckBoxWithCombo ViewModel then derive from the abstract base class.
-
由 Balaji Krishnan 提交于
Rename several internal types appropriately. Update file names to match them. etc.
-
由 Balaji Krishnan 提交于
Adding Enforcement Levels to each `use var` option. Enforcement levels are: None, Info, Warning and Error. To do: unit tests need to be unbroken refactoring to base classes and to be more generic fix xaml styling and remove any hardcoded values. fix up todo comments in code
-
由 Balaji Krishnan 提交于
These are additive minor changes to code naming, styling, documentation, tests and such. No major functional changes.
-
由 Balaji Krishnan 提交于
-
由 Balaji Krishnan 提交于
We now detect a conversion, if any, do not suggest use var if it changes semantics, as it would for some implicit conversions. We also recognize type conversion patterns for IsTypeApparent(). For e.g., we recognize static helpers like `int.Parse`, `Convert.ToString()` and instance method `IConvertible.ToChar` etc.
-
由 Balaji Krishnan 提交于
localize all the string resources for use var or use explicit typing analyzers and fixers.
-
由 Balaji Krishnan 提交于
Changed the UI from combinations of radio buttons and check boxes to use just checkboxes. Also changed how the partitions of `use var` space was logically represented. We now present 3 options - use var on intrinsic types, use var where apparent, use var in rest of the places. If all 3 are checked, we universally use var everywhere. If only one or a combination less than 3 are selected, we use var only in those places. An unchecked option means, user prefers explicit typing for that scenario. Not yet implemented : enforcement levels of the fix, fancy previews that show results for a combination of choices, integrating the options into code generation service.
-
由 Balaji Krishnan 提交于
Remove relay command implementation and usages in checkbox view model. trying another UI approach to make this simpler.
-
由 Balaji Krishnan 提交于
Add RelayCommand to CheckBoxViewModel to enable/disable checkboxes in option preview control depending on the state of other controls. The StyleViewModel now makes use of this for Use Var feature.
-
由 Balaji Krishnan 提交于
Refactor UseImplicitTyping and UseExplicitTyping Analyzers to use an abstract base class and share common functionalities. Also wire up options into unit tests.
-
由 Balaji Krishnan 提交于
add options to codestyle for use implicit or explicit typing analyzer/fixers.
-
由 Balaji Krishnan 提交于
Add an analyzer and fixer for using explicit type over var for C#. Plus, unit tests.
-
由 Balaji Krishnan 提交于
Add logic to determine if return type information is obvious from the initializer expression of variable declaration. Currently it recognizes 3 patterns - literals, object creation expressions and static helpers like `int.Parse`
-
由 Balaji Krishnan 提交于
shelving, edit this commit later.
-
由 Balaji Krishnan 提交于
Initial implementation of a diagnostic analyzer and codefixer for `use var` style in C#
-
由 Artur Spychaj 提交于
Conflicts: build/Targets/VSL.Versions.targets build/scripts/VBCSCompiler.exe.config build/scripts/csc.exe.config build/scripts/vbc.exe.config cibuild.cmd src/Compilers/CSharp/csc/csc.exe.config src/Compilers/VisualBasic/vbc/vbc.exe.config src/Interactive/VbiCore/project.lock.json src/InteractiveWindow/Version.props src/VisualStudio/Core/Def/Implementation/ProjectSystem/VisualStudioWorkspaceImpl.cs src/VisualStudio/Setup/ProvideRoslynBindingRedirection.cs
-
- 23 2月, 2016 1 次提交
-
-
由 David Kean 提交于
fix issue 8315
-