plocket
commented
1 year ago Thanks for the issue! Adding a little commentary:
better couple the installation interview with the running interview, and make it easier to discover from the running tests interview.
Sorry I didn't describe clearly - currently the installation and test running are completely coupled. The presentation didn't make that clear and I should add a slide. I was actually suggesting making them less coupled and having two separate interviews, but somehow making the installation interview very discoverable (as the suggestion above describes)
complete couple the installed version of Kiln with the installed version of this package; then, to change the installed version of kiln, you do it through the same interface you handle different docassemble packages with
The pro here is that it would be the same workflow as folks use for their other packages. The con would be that it would be hard for folks to go back to previous versions. Occurred to me later: Currently this worries me as I think ALKiln is still in its infancy, or at least still young, and I want devs to be able to easily revert if they need to. Especially once we have shrinkwrap in place - that way they'll be sure of the dependencies as well.
Problem: developers might want to install and handle different version on Kiln through npm. Currently, they handle that through an entirely different interview process that would let them change the installed version.
Solutions: