Skip to content

v0.5.1: warn about repaired member names on table downloads - #172

Merged
mountainMath merged 11 commits into
masterfrom
v0.5.1
Sep 16, 2026
Merged

mountainMath merged 11 commits into
masterfrom
v0.5.1

Conversation

@mountainMath

Copy link
Copy Markdown
Owner

Summary

  • Table downloads now warn about member labels that were repaired of non-breaking spaces and control characters, the same way they already warn about column names. A table whose column names are clean but whose labels carry the characters, for example the province names in 13-10-0383, was repaired silently because the metadata parser assumed the column name warning had already covered it. Every download path (get_cansim(), get_cansim_connection() with parquet and sqlite) reports it once, reads from cache stay silent, and options(cansim.suppress_repair_warnings=TRUE) silences it (Special characters in column names #169)
  • Version bumped to 0.5.1 in DESCRIPTION and the README citation
  • The NEWS section for the last release was still headed 0.4.5 although it shipped to CRAN as 0.5.0, so it is relabelled and a 0.5.1 section opened

Test plan

  • test-character_repair.R and test-cache_info.R pass with and without NOT_CRAN=true
  • New test downloads 13-10-0383 and checks the warning names the table, shows Newfoundland<U+00A0>and Labrador, counts four repaired names, and is suppressed by the option
  • Verified by hand that the parquet and sqlite connection paths warn once and the French download is silent since its labels are clean

🤖 Generated with Claude Code

mountainMath and others added 11 commits September 15, 2026 16:09
A table whose column names are clean but whose member labels carry a
non-breaking space was repaired silently, since the metadata parser
assumed the column name warning had already covered it. Give the member
name repair its own context so every download path reports it once.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The NEWS section for the last release was still headed 0.4.5 although it
shipped to CRAN as 0.5.0, so relabel it and open a 0.5.1 section for the
member name warning.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The repair warnings and the no-data warning for vectors were wrapped to
getOption("width") when raised, which matched the window only by luck
and put line breaks in the middle of sentences in RStudio panes,
knitted documents and resized terminals. Each sentence now starts on
its own line and the window wraps the rest at its actual width.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Three vignettes had been excluded from the CRAN build via .Rbuildignore
since 2018 and were only available on the pkgdown site.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Bring cran-comments.md up to date: the section describing the previous
release was labelled 0.4.5 but that version was never published, it went
out as 0.5.0. Add the 0.5.1 section. Fix three spelling mistakes in
documentation found by spelling::spell_check_package().

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The finetuned warning joins the two closing sentences with a comma, so
"this warning" is no longer capitalized. The test is network-only and
skipped on CRAN, which is why the check passed with the stale text.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The chunk-level eval option keyed to COMPILE_VIG does not apply to
inline `r ...` expressions in prose. Two of the restored vignettes had
three such expressions, one calling search_cansim_cubes() over the
network and two using variables only defined in unevaluated chunks,
which failed the CRAN incoming pretest. They now fall back to fixed
text when the vignettes are not being compiled.

Also note the resubmission in cran-comments.md.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mountainMath
mountainMath merged commit df73198 into master Sep 16, 2026
5 checks passed
@mountainMath
mountainMath deleted the v0.5.1 branch September 16, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant