0.14.0...0.15.0

View the full list of issues and PRs

0.13.0...0.14.0

View the full list of issues and PRs

What's Changed

• Fix tool command name on README by@augustoproiete in#14
• Fix#15 "An item with the same key has already been added." by@nightroman in#16
• Fixes the build and update to latest .NET SDK by@Mpdreamz in#19
• Update CI builds to use latest .NET SDK by@Mpdreamz in#20
• Fixes#13 exposed properties should read most recent Section by@Mpdreamz in#21
• Fix#17 ensure xmldocs are available by@Mpdreamz in#22

New Contributors

• @augustoproiete made their first contribution in#14
• @nightroman made their first contribution in#16

Full Changelog:0.12.2...0.13.0

Contributors

0.12.1...0.12.2

New Features

• #6 Remake glob matcher (minimatcher) to significantly improve performance
• #9 [netstandard] Migrated EditorConfig.Core project to support multiple … (issue:#2)
• #10 Change ParseFile to an overload to Parse and make it public
• #11 Update build to make it easier to release

View the full list of issues and PRs

Added properaspnetcore50 andnet45 builds.

This is the first release of the .net port of editorconfig core:

The .NET port was necessary in order for crossplatform .NET code to take advantage of editorconfig files without having to link against different c libraries for different platforms.

command line

https://chocolatey.org/packages/editorconfig.core (still pending approval of 0.12.0)

The chocolatey package now uses the .net port of the cli tooling.

library

http://www.nuget.org/packages/editorconfig/

Providesstrongly typed access to your editorconfig configuration for files. See theREADME for more information.

The nuget package is intended for when you want to embed support for reading editorconfig files i.e: editor extensions (visual studio/xamarin/others).

future work

• moving the visual studio extension to the .NET library, this will make it easier to compile without requiring CMAKE.
• Looking to add support for editorconfig insidehttp://github.com/omnisharp so that refactorings take.editorconfig files into account and to use.editorconfig domain properties to configure omnisharp itself