1. 10 10月, 2018 1 次提交
  2. 06 10月, 2018 2 次提交
  3. 05 10月, 2018 1 次提交
  4. 03 10月, 2018 3 次提交
  5. 02 10月, 2018 7 次提交
  6. 29 9月, 2018 1 次提交
  7. 27 9月, 2018 4 次提交
  8. 26 9月, 2018 3 次提交
  9. 25 9月, 2018 1 次提交
  10. 24 9月, 2018 4 次提交
  11. 23 9月, 2018 1 次提交
  12. 22 9月, 2018 5 次提交
  13. 21 9月, 2018 5 次提交
  14. 20 9月, 2018 2 次提交
    • M
      Mark a field read-only · 356e3140
      Manish Vasani 提交于
      356e3140
    • M
      Add support to save current tools options into an .editorconfig file · 588f1798
      Manish Vasani 提交于
      This ports https://github.com/dotnet/roslyn/pull/28472, that went into the `editorconfig-ide` feature branch, into `dev16.0.x` branch with following additional refactorings/enhancements:
      
      1. Generated .editorconfig file has all localized string as comments.
      2. No hardcoding of individual options in the editorconfig file generator. Instead, each `EditorConfigStorageLocation` now requires to provide a delegate to convert a given option value into the .editorconfig string representation (basically complimentary of the parsing delegate that was already required).
      3. Introduce concept of `OptionGroup` to enable grouping options in the same feature (such as CodeStyleOptions, CSharpCodeStyleOptions, FormattingOptions, CSharpFormattingOptions, etc.) into sub-features or groups (such as "this. preferences", "expression-level preferences", etc.). This enables the editorconfig generation to group the related options, without explicit knowledge of each option group.
      4. Expose `AllOptions` from each option feature (such as CodeStyleOptions, CSharpCodeStyleOptions, FormattingOptions, CSharpFormattingOptions, etc.), so that the corresponding `IOptionProvider` always stays in sync with implemented options.
      588f1798