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
Presumably, x$pre is supposed to be the preprocessor, but it actually partial-matches to x$predictions.
musing: if not for this coincidence, warnPartialMatchDollar wouldn't have even caught this and we'd just be testing vs. NULL. This is also an issue for epi_archives. (And also epi_dfs though for attrs not list elts.) Is there any sort of list subclass that makes $/attr do exact matches and produce an error rather than NULL when the requested key has no match?
The text was updated successfully, but these errors were encountered:
Hey could you tag these new issues with priority + size estimates and bucket them into backlog/icebox please? Should be easiest when freshly filed and the context is clear.
epipredict/R/canned-epipred.R
Line 115 in 7f08d40
Presumably,
x$pre
is supposed to be the preprocessor, but it actually partial-matches tox$predictions
.musing: if not for this coincidence,
warnPartialMatchDollar
wouldn't have even caught this and we'd just be testing vs.NULL
. This is also an issue forepi_archive
s. (And alsoepi_df
s though for attrs not list elts.) Is there any sort of list subclass that makes$
/attr
do exact matches and produce an error rather thanNULL
when the requested key has no match?The text was updated successfully, but these errors were encountered: