Follow-up to #3572

[MichaelChirico]

Jan had some extra feedback on #3572.

Regarding the <code> block in the header, I think that's just a GitLab issue. title YAML field is supposed to go into the browser tab, I thought... I guess GitLab is not using MultiMarkdown, or something like that? The datatable-intro vignette has the same issue on Gitlab but it renders correctly on CRAN, so ignoring that part.

[codecov]

Codecov Report

Merging #3593 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3593   +/-   ##
=======================================
  Coverage   97.63%   97.63%           
=======================================
  Files          66       66           
  Lines       12721    12721           
=======================================
  Hits        12420    12420           
  Misses        301      301

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df28194...1cbf466. Read the comment docs.

[codecov]

Codecov Report

Merging #3593 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3593   +/-   ##
=======================================
  Coverage   97.63%   97.63%           
=======================================
  Files          66       66           
  Lines       12721    12721           
=======================================
  Hits        12420    12420           
  Misses        301      301

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df28194...1cbf466. Read the comment docs.

[jangorecki]

It is not strictly related to GitLab, I am getting same <code> after rendering vignette locally on my laptop. I think CRAN uses some pandoc configuration that handles that better.