Split update-system into build-system and try-action-system

[tangrammer]

Hi Stuart,
I was wondering if it makes sense to you splitting this update-system behaviour so we could have build-system fn that only assoc-dependencies and try-action fn that try-action

I'm trying to intercept system components and this update-system function is a really security box to try that :) I'd need to have the system build, then intercept selected components and after that try start fn on system

Thanks in advance
Juan

[stuartsierra]

You can get that by calling update-system with identity as the action.

[tangrammer]

That's a really (and great) functional solution!
I didn't realise how easy could be to call my own fn wrapping component/start too

Anyway still need a bit more data so I did this PR #20 to be more clear about it

Thanks again!
Juan

[tangrammer]

Hi Stuart,
I'm closing PR #20 after realising again that this update-system fn with any function and any arguments is a really good (and functional) way to work and transform the system
In my case I get co-dependency relations using a mutable ref of the system (atom) as argument and worked!
https://github.com/tangrammer/co-dependency/blob/master/src/tangrammer/co_dependency.clj#L55

Thanks!
Juan