Skip to content
This repository has been archived by the owner on Sep 7, 2021. It is now read-only.

Should data.specifications explicitly exclude the CSSInfo macro? #517

Open
ddbeck opened this issue Jul 17, 2020 · 0 comments
Open

Should data.specifications explicitly exclude the CSSInfo macro? #517

ddbeck opened this issue Jul 17, 2020 · 0 comments

Comments

@ddbeck
Copy link
Contributor

ddbeck commented Jul 17, 2020

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant