-
Notifications
You must be signed in to change notification settings - Fork 158
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
Live refresh/Hot reload #627
Comments
Sounds good Kevin, I think I should make you Co admin on this repot and nuget (I'm on vacation and haven't republished the nuget yet) |
Kevin, what's your nuget id please? |
I'll be glad to help where I can, sorry to have bothered you during vacation, enjoy the rest of it ;). My nuget profile is here: https://www.nuget.org/profiles/Mutagene. |
@kMutagene I've sent the request on nuget |
@dsyme thank you! I was just writing the release docs for the next package (feels a little strange to write those about commits that are not my own) and wondering about #621 and how that commit affects the version number of the next package, will it be 8.0 or 7.3? When that is sorted i will release the package today |
@kMutagene When in doubt bump the major version :-) |
* Add server side hot reload message cycling for the watch command * Add substitution-based injection of hot reload script into templates * add note for watch script to styling docs * Incorporate review-requested changes Co-authored-by: Don Syme <[email protected]>
Closed as of #629 |
Currently, when developing docs via
fsdocs watch
, one has to manually reload the browser page after the new files are generated. As this project uses Suave, it should be possible to mirror the changes of this PR to fornax, which implemented live refresh there.The text was updated successfully, but these errors were encountered: