As explained in Issue #26, this will decouple the code and tests from dependence on Prolog::Core entities beyond duck-type compatibility. As mentioned in the issue, breaking out separate query objects is also a desirable, and relatively high value-for-cost, enhancement as well.
Listed as a 'bug' because, as the issue pointed out, explicit dependencies are a bug. Listed as a 'enhancement' because the query objects add value but are not, strictly speaking, defect repair.
This should be the final bit blocking release of Gem Release 0.7.0. :sweat_smile:
As explained in Issue #26, this will decouple the code and tests from dependence on
Prolog::Coreentities beyond duck-type compatibility. As mentioned in the issue, breaking out separate query objects is also a desirable, and relatively high value-for-cost, enhancement as well.Listed as a 'bug' because, as the issue pointed out, explicit dependencies are a bug. Listed as a 'enhancement' because the query objects add value but are not, strictly speaking, defect repair.
This should be the final bit blocking release of Gem Release 0.7.0. :sweat_smile: