Feature/dev live reload#322
Conversation
- Add LiveReload middleware for injecting WebSocket client script - Add live reload settings to GlobalSettings - Update server to start live reload server in development mode - Fix WebSocket client handling in live reload server - Add comprehensive tests for live reload functionality
- Update middleware test to match SSE implementation - Add handler tests for SSE endpoint - Fix server tests for file watching - Update deprecated sleep calls to use Time::Span
- Fix event handler reassignment in live reload script - Update middleware test to use call instead of chain
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Hey! 👋 Thanks a lot for opening this PR! I agree that live reloading could be useful for some Marten projects. However, I’m not sure it’s something that should live within the framework itself — many projects can (and do) use external tools for live- or hot-reloading, and the need might not be common enough to justify maintaining it as part of Marten. I think it would make a great standalone shard though. Would you be open to creating one? |
|
[jj.monitor] Branch is 106 commits behind The 14 failing CI checks (crystal, generated-project, postgres matrix, generated-auth-project) are downstream of the staleness, not all independent issues — they need re-running against a freshly-rebased branch before they're meaningful signal. Recommend rebasing onto current
|
…rten # Conflicts: # src/marten/server.cr
2 participants
No description provided.