Discussion: Consider support for a “debug” mode?

[theengineear]

In both the XElement base class and the TemplateEngine class — we could consider adding a debug mode which could change the behavior of error reporting. This could also look like a “strict mode” as well.

The development flow would be to develop locally in some sort of strict mode where we’re willing to take some performance hits to gain insights. But, in production environments, this flag could be off — re-capturing performance where developer insights are not as important.

Things we could add in strict mode.

• Stricter parsing of input html strings in the TemplateEngine. We could enforce more rules and also spend more effort reporting when things look off.
• Others?

Things we could ditch in production.

• It may not be necessary to do static analysis validation in production.
• It may not be necessary to do runtime type checking in production.

[theengineear]

I’m not yet sure where I land on this one. I think if anything — it would be cool to have a stricter mode when developing locally. But, I’m not sure if it would actually be a good idea to loosen any validations in production just yet.

Anyhow… this topic has come up on-and-off quite a bit, so I figured it’d be worth tracking with an issue thread.