Three rules read the declared level. None of them read its other copy.
Our submission template asks a package to declare one thing: its contribution level -- case study , system , or theory+empirics . Three separate rules read that field. Last week a submission passed all three while carrying two different values for it . The reason is one sentence long: a package states its level in more than one carrier, and every rule we had compared one copy of it against the…
Three distinct rules oversee a package's declared contribution level, which can be categorized as case study, system, or theory+empirics. These rules examine three separate sources: the registration target field, the manuscript's own declaration, and the package's README.md file. Despite the presence of three carriers for the level, none of the three rules compare the different copies of the level to ensure consistency.
This oversight allows a submission to pass all three tests even when it carries two different values for its contribution level. Consequently, a package might declare theory + empirics in its registration, while the manuscript reads empirics, and the package's README.md remains at theory + empirics.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
