You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to reproduce a different issue I ran into an issue with uploading a single feature file that is in the current folder. For example, using the following command will fail:
Starting publishing of feature files...
An exception occured while uploading feature file 'MyFeatureFile.feature
System.ArgumentException: Path cannot be the empty string or all whitespace.
Parameter name: path
at System.IO.Directory.SetCurrentDirectory(String path)
at Augurk.CommandLine.Commands.PublishCommand.ParseFeatureFile(String featureFile) in d:\a\1\s\src\Augurk.CommandLine\Commands\PublishCommand.cs:line 272
at Augurk.CommandLine.Commands.PublishCommand.PublishFeatureFiles() in d:\a\1\s\src\Augurk.CommandLine\Commands\PublishCommand.cs:line 97
This looks to be related to this piece of code. We're trying to change the current directory to the directory of the feature file, but if the provided feature file is a relative path this will probably return null resulting in the exception.
Perhaps we should make all the feature files provided on the command line into absolute paths first, before running this logic. Will need to look into that.
The text was updated successfully, but these errors were encountered:
While trying to reproduce a different issue I ran into an issue with uploading a single feature file that is in the current folder. For example, using the following command will fail:
This results in the following exception:
This looks to be related to this piece of code. We're trying to change the current directory to the directory of the feature file, but if the provided feature file is a relative path this will probably return null resulting in the exception.
Perhaps we should make all the feature files provided on the command line into absolute paths first, before running this logic. Will need to look into that.
The text was updated successfully, but these errors were encountered: