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
My expected behavior of fsdocs --watch is that it would be like dotnet watch where when changes to files were made, fsdocs would build again and update the output files. I have reviewed the hot-reload PR that was merged, so it should update the browser with the new generated files. I want to make sure that is what the intent is, right? Mine is not doing that. Doing watch does the initial launch and then says some websocket errors and shutdown messages and leave the blinking courser on an blank line. If i hit enter, the > prompt comes back and fsdocs has ended.
If the watch is supposed to flow as i described previously, I will test on clean windows and linux (Debian) and supply a detailed report of the findings.
The text was updated successfully, but these errors were encountered:
You will need to ensure that the input directory exists, and contains at least index.md, otherwise the browser will report an error (e.g. "Problem loading...", "Connection was reset").
My expected behavior of
fsdocs --watch
is that it would be likedotnet watch
where when changes to files were made, fsdocs would build again and update the output files. I have reviewed the hot-reload PR that was merged, so it should update the browser with the new generated files. I want to make sure that is what the intent is, right? Mine is not doing that. Doing watch does the initial launch and then says some websocket errors and shutdown messages and leave the blinking courser on an blank line. If i hit enter, the > prompt comes back and fsdocs has ended.If the watch is supposed to flow as i described previously, I will test on clean windows and linux (Debian) and supply a detailed report of the findings.
The text was updated successfully, but these errors were encountered: