when foo.lsm.html doesn't exist does not cause a sensible early exit and error message. Instead it will get all the way to the model array construction step before barfing. This should be caught at the same point as we detect whether things are columns/lsms/etc.
JSKenyon
commented
4 years ago
Basically, running:
when
foo.lsm.htmldoesn't exist does not cause a sensible early exit and error message. Instead it will get all the way to the model array construction step before barfing. This should be caught at the same point as we detect whether things are columns/lsms/etc.