Conversation
thanks to @mwmiller for the feedback
@moollaza @killerfish Here is my even crazier take on how to organize the data. I've got some of each of your ideas in here. That array of hashrefs very much wants to become an array of objects, but that will be for another day, if ever. |
Its perfect, i was also thinking along the lines to make this an attribute, but didnt see the use for that, cleanup of New.pm justifies it for me. |
@killerfish I think it's a ways from "perfect", but I thank you for the kind words. 😁 Regardless, I also have this as a suggested first step towards more sane logging. I don't want to open a PR until it become clear how these branches will come together, because many of the places where the improved logging gets used are in flux. |
@mwmiller your approach is awesome. Let's do it :) |
- Expose a singular hashref with directory and related info. - Use a more platform independent way of constructing directories. Except that IO::All thwarts this. This could definitely use some cleanup (and probably some actual Type Objects), but the basic idea is here.
Toward better logging, here's a simple routine to print a supplied message and then exit with the supplied code.
They can still be jerks and enter invalid things, but maybe we will notice later.
@moollaza @killerfish I've merged in the two mentioned branches (the data reorg and the |
Tested a bunch in different repos. Only fix I'd like to make is that DuckPAN server still runs for Fathead as expected and then fails hard after making a request. This is unrealted to this code, but can be alleviated by utilizing the new functionality :) |
thanks to @mwmiller for the feedback
cc// @mwmiller
also @killerfish I made a new fn to check the current directory, get they type of IA we're working with and error out if it's Longtail or Fathead
Would appreciate any feedback :)
Note this has two accompanying change to the Spice and Goodie templates