Augurk.CommandLine 3.2.1

Prefix Reserved
dotnet add package Augurk.CommandLine --version 3.2.1                
NuGet\Install-Package Augurk.CommandLine -Version 3.2.1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Augurk.CommandLine" Version="3.2.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Augurk.CommandLine --version 3.2.1                
#r "nuget: Augurk.CommandLine, 3.2.1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Augurk.CommandLine as a Cake Addin
#addin nuget:?package=Augurk.CommandLine&version=3.2.1

// Install Augurk.CommandLine as a Cake Tool
#tool nuget:?package=Augurk.CommandLine&version=3.2.1                

Command line tools for publishing feature files to Augurk.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
3.2.1 14,700 10/25/2017
3.2.0 1,948 7/12/2017
3.1.1 1,085 5/30/2017
3.1.1-pullrequest0007 770 5/30/2017
3.1.0 975 4/7/2017
3.0.0 1,102 1/25/2017
2.4.0 1,329 1/11/2017
2.3.2 1,147 1/10/2017
2.3.1.1 1,244 11/4/2016
2.3.0 1,510 1/12/2016
2.2.0 1,444 12/16/2015

This version integrates the new Gherkin parser instead of relying on the old SpecFlow specific parser. This makes
     the total package a lot smaller as well. Due to some subtle differences in parsing (mainly indentation at the start of
     a line in feature and scenario descriptions are now preserved), there is now a --compat-level flag that can be set to 2
     (or lower) if necessary to fallback to the previous behavior.
     
     Fixed a bug in PublishCommand that caused an error to occur when a relative directory containing multiple feature-files
     was specified using the --featureFiles argument (see issue #6).