You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2021. It is now read-only.
While fixing CSS pages' errors, I've noticed a pattern: when I add data.formal_definition (which includes a {{CSSInfo}} call), I check the page for that macro call elsewhere. It's usually in the data.specifications section and I delete it.
That is, if I remember to look and make the change. It occurred to me that we could regularize this check by either explicitly forbidding macros other than SpecName from data.specifications or, more narrowly, forbidding the CSSInfo macro from the ingredient.
This would be a pretty easy change to make to the spec and ingredient handler. Should we do it? What considerations might I be missing? I'd appreciate your input on this @Elchi3, @wbamberg, and @chrisdavidmills.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While fixing CSS pages' errors, I've noticed a pattern: when I add
data.formal_definition
(which includes a{{CSSInfo}}
call), I check the page for that macro call elsewhere. It's usually in thedata.specifications
section and I delete it.That is, if I remember to look and make the change. It occurred to me that we could regularize this check by either explicitly forbidding macros other than
SpecName
fromdata.specifications
or, more narrowly, forbidding theCSSInfo
macro from the ingredient.This would be a pretty easy change to make to the spec and ingredient handler. Should we do it? What considerations might I be missing? I'd appreciate your input on this @Elchi3, @wbamberg, and @chrisdavidmills.
The text was updated successfully, but these errors were encountered: