Note that this does not affect the underlying prolog_core which, as of Gem version 0.4.0, does depend on it. We don't care here.
This is being done to avoid the Gordian knots involved in testing and decomposing use-case classes, per the running discussion in Issue #5. PR #6 will be closed and a new PR opened to create a new RegisterNewMember use case not dependent on Wisper.
Note that this does not affect the underlying
prolog_core
which, as of Gem version 0.4.0, does depend on it. We don't care here.This is being done to avoid the Gordian knots involved in testing and decomposing use-case classes, per the running discussion in Issue #5. PR #6 will be closed and a new PR opened to create a new
RegisterNewMember
use case not dependent on Wisper.