SeaGL
Fail the build on undefined variables
Currently if you mistype a variable name or delete a variable that’s still in use Jekyll will silently ignore the error. Want to enable its strict mode to fail the build instead?
Due to Shopify/liquid#1034 working with deliberately undefined variables is a pain but I’d prefer to make the tradeoff.
These changes makes sense to me, but I don't feel confident in doing a code-review. Trust your judgement if they are ready to go live.
I think it’s mostly a matter of preference;
- If there’s a mistake in an edit, would we rather the site be published as-is or held back for correction?
- Is it okay that I un-parameterized some content in old blog posts? Last time I did that there were objections.
Gotcha, I am pretty fine with things being held back for corrections, as long as notification is raised. In terms of un-parameterized content, can you give an example? Perhaps I didn't read the past objections as closely as I should have...
#247 initially included fa9c023 to avoid rewriting history with mangled links, but Ben suggested omitting this step, you +1’d his position, Nathan defended it, and I yielded to consensus. I still don’t really understand the objection so it’s hard for me to predict whether it also applies to this PR.
Still going in circles trying to figure this out, I blame some of the double negatives in comments related to that issue...
IMHO, we want parameterization in general, we just don't want to have Freenode linked anywhere. Removing parameters from old posts is A-okay with me. There is some world where the word wasn't parameterized, but just the link, and I think that's where some confusion perhaps came from?
@AndrewKvalheim What's the status of this PR? Should it be closed at this point?
Available, should we want it. Probably nice to have, but potentially a nuisance for casual editing.
Personally I lean toward keeping slow issues open, but I understand that it’s also popular to hide and deliberately forget about them.