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
Let's say I have an integrant system with multiple components and I want to debug one of them.
For that, I need to be able to access the resolved config of that component, to be able to call functions at the repl, and analyze the component's behavior.
Reading the issues, #45 was a similar request, but the proposed solution doesn't solve my issue, because ig/resolve-key requires to modify existing production code and I don't want to do that.
Is there a way to do that without touching the config at all ?
The text was updated successfully, but these errors were encountered:
You'd need to add in some manner of debugging. For example you could attached the resolved config via metadata, or keep it in an atom, or log it to STDERR or a file, or any of the other usual mechanisms we have for analyzing intermediate data within a program.
Let's say I have an integrant system with multiple components and I want to debug one of them.
For that, I need to be able to access the resolved config of that component, to be able to call functions at the repl, and analyze the component's behavior.
Reading the issues, #45 was a similar request, but the proposed solution doesn't solve my issue, because
ig/resolve-key
requires to modify existing production code and I don't want to do that.Is there a way to do that without touching the config at all ?
The text was updated successfully, but these errors were encountered: