Jamie Stormbreaker

@smith I think that's the right approach

It's reasonable to question the implementation for sure. I think it's a good choice to go forward with TOML since that's the format we've chosen for almost nearly everything else....

@raskchanky that's an interesting approach for sure. We also won't need to write any docs no our non-standard validation language ;)

@eeyun and I just had a chat about this and we're going to make some small changes to how we triage issues so this doesn't happen again :)

@danielsdeleo absolutely, I particularly think the english/human readable version is the way to go

This behaviour is coming from our handlebars renderer. Undefined variables don't result in rendering errors in handlebars, so they're happily rendered in our configuration and hook files as well. We...

@moretea I think you wanted to link to another issue, that's the number of this one :). Did you mean #2281 by chance?

We probably want to have some sort of escape mechanism for the Supervisor while in the Studio which disables the secret comparison in the connection handshake. It's really not necessary...

I think it's a little bit too "magic" that somebody would need to know what the default whitelist is. I wouldn't want to be on the receiving end of trying...

Not quite yet, #4805 is a predecessor for the change which will address this