Hi @U0522TWDA. Github claims that there are conflicts that need to be merged. Would you please investigate and address? I briefly looked over the changes visually and they seem reasonable - given my limited understanding of the cryogen code. Overall, though, I have concerns that by just compiling the changed files, the whole blog is left in an inconsistent state. Furthermore, this is a breaking change in the behavior of the system, which might catch some folks off guard. For example, those that start up a server and push changes to file without re-starting the server. One approach to address my concerns would be to put this change behind a configuration parameter, but with the obvious drawback of the additional complexity of yet another config key. Perhaps also add something to the docs that mentions this changed behavior Being relatively new to cryogen, I'd like input on this from others @U0DJK1VH6 and @U050CBXUZ . I might also be over-thinking this, and my concerns may not be an issue in practice?

Carmen and Dmitri gave their LGTM here https://clojurians.zulipchat.com/#narrow/stream/180378-slack-archive/topic/cryogen/near/215103821, scroll up few posts and back to follow the discussion where Carmen had the same proposal as you about a flag but retracted it eventually after I explained the opt-in .

Thanks to the pointer to the previous discussions. I had not realized it was opt-in. I see that now. Thanks for fixing the conflicts. Github says there are conflicts on the associated PR220 on the cryogen repo. Once you resolve that conflict, I can test out both PRs and merge them. One note - this PR#149 changes the version in project.clj. Perhaps it should be changed to 0.4.1-SNAPSHOT? Or perhaps this PR should not change the version at all, and the version should be changed only when a coordinated set of changes are made?

Thanks, conflict fixed

Regarding the version: I think it is good practice to change it since this is not part of 0.4.0 and being -SNAPSHOT it is clear it is not made for release. When we decide to make a release, then we change it to whatever we see appropriate and release. But if you prefer, I can drop the version change. Ideally, IMHO, the version would already have been "NEXT" but maven does not support that 🙂

Okay. Thanks. I have to step out right now, but will review and merge later. The version issue is another thing that could be discussed in #cryogen .

@U0522TWDA I reviewed and merged cryogen-core PR#152 and the corresponding cryogen-docs PR#39

I also noticed that the PR bumped up the version.

Right. Perhaps we should write down guidelines for when, how to bump the version?