On Tue, Nov 10, 2015 at 9:18 AM, Adam Brightwell
<adam.brightwell@crunchydata.com> wrote:
>> I'm with Alvaro: the most interesting question here is why that mistake
>> did not blow up on you immediately. I thought we had enough safeguards
>> in place to catch this type of error.
>
> Ok, I'll explore that a bit further as I was able to build and use
> with my hook without any issue. :-/
Ok, I have verified that it does indeed eventually raise a warning
about this. It took a few for it to occur/appear in my logs. I was
expecting it to be more "immediate". At any rate, I don't believe
there are any issues with the safeguards in place.
-Adam
