Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.ArgumentException: The directory name 'docs' does not exist. #632

Closed
vilinski opened this issue Jan 16, 2021 · 0 comments · Fixed by #641
Closed

System.ArgumentException: The directory name 'docs' does not exist. #632

vilinski opened this issue Jan 16, 2021 · 0 comments · Fixed by #641

Comments

@vilinski
Copy link

vilinski commented Jan 16, 2021

Already mentioned this in #620. The same behavior in version 8.0. Exception if the repository has no docs folder yet.

$ fsdocs watch --eval

...
...
  registering entities for assembly ifm.Suite.Libraries.InMemoryMessageBus...
Error :
StopProcessingExn
Unhandled exception. System.ArgumentException: The directory name 'docs' does not exist. (Parameter 'path')
   at System.IO.FileSystemWatcher.CheckPathValidity(String path)
   at System.IO.FileSystemWatcher..ctor(String path)
   at FSharp.Formatting.CommandTool.CoreBuildOptions.Execute() in C:\Users\Kevin\source\repos\fsprojects\FSharp.Formatting\src\FSharp.Formatting.CommandTool\BuildCommand.fs:line 669
   at [email protected](WatchCommand opts) in C:\Users\Kevin\source\repos\fsprojects\FSharp.Formatting\src\FSharp.Formatting.CommandTool\Program.fs:line 10
   at CommandLine.ParserResultExtensions.MapResult[T1,T2,TResult](ParserResult`1 result, Func`2 parsedFunc1, Func`2 parsedFunc2, Func`2 notParsedFunc)
   at FSharp.Formatting.CommandTool.Main.main(String[] argv) in C:\Users\Kevin\source\repos\fsprojects\FSharp.Formatting\src\FSharp.Formatting.CommandTool\Program.fs:line 7
[1]    14664 abort      fsdocs watch --eval
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant